-
Notifications
You must be signed in to change notification settings - Fork 323
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
Correct webhook-cert-manager-clusterrole to utilize the web-cert-manager podsecuritypolicy rather than connect-injectors when global.EnablePodSecurityPolicies is true. #1202
Conversation
resourceNames: | ||
- {{ template "consul.fullname" . }}-webhook-cert-manager | ||
verbs: | ||
- use |
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 think the part below is a bug. It should be using the cert-manager policy.
resourceNames: | ||
- {{ template "consul.fullname" . }}-webhook-cert-manager | ||
verbs: | ||
- use | ||
- apiGroups: | ||
- policy |
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.
You can just rename the connect-injector to be the webhook-cert-manager. It being connect-injector is a bug!
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.
Thanks so much for investigating this!!
We can still remove the controller from the sync test as the test does not actually require a controller to run! |
👍 I'll merge that other PR tomorrow after we confirm the nightly tests are all set. |
Co-authored-by: Luke Kysow <[email protected]>
Changes proposed in this PR:
How I've tested this PR:
How I expect reviewers to test this PR:
👀
Checklist: