-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Fix kube-proxy PodSecurityPolicy RoleBinding namespace #72761
Conversation
/assign @cadmuxe |
@tallclair: GitHub didn't allow me to assign the following users: cadmuxe. Note that only kubernetes members and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign @bowei |
/lgtm |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bowei, tallclair The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest Review the full test history for this PR. Silence the bot with an |
1 similar comment
/retest Review the full test history for this PR. Silence the bot with an |
/retest |
1 similar comment
/retest |
/retest Review the full test history for this PR. Silence the bot with an |
…761-upstream-release-1.11 Automated cherry pick of #72761 upstream release 1.11
…761-upstream-release-1.12 Automated cherry pick of #72761 upstream release 1.12
What type of PR is this?
/kind bug
What this PR does / why we need it:
kube-proxy's PodSecurityPolicy binding was accidentally created in the default namespace rather than
kube-system
Does this PR introduce a user-facing change?:
/sig gce
/priority important-soon