-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added support for PodSecurityPolicy #992
Conversation
ok to test |
OK to test |
if (kind.endsWith("ses")) { | ||
kind = kind.substring(0, kind.length() - 2); | ||
} else if (kind.endsWith("s")) { | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@piyush1594 this is really good catch! 👍
retest this please |
1 similar comment
retest this please |
Please rebase this PR to align the dependency to the latest kube-model |
Yes, @oscerd just realised and did that |
[merge] |
|
||
@After | ||
public void cleanup() { | ||
client.podSecurityPolicies().delete(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I missed this in the initial part of the review. It's not a good idea to delete all the PodSecurityPolicy objects since they are not a namespace specific resource. Instead, you should simply delete the resource you created during test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes @rohanKanojia, you seem correct will send a quick PR.
#969