-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Cherry-pick metadata-agent psp binding #70497
Cherry-pick metadata-agent psp binding #70497
Conversation
@tallclair: GitHub didn't allow me to assign the following users: davidebelloni. Note that only kubernetes members and repo collaborators can be assigned. 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. |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kawych, 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 |
1 similar comment
/retest |
ping @foxish for cherrypick approval |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Cherry-pick the PodSecurityPolicy binding for the metadata-agent addon to release-1.11. This is required for the metadata-agent to work with PodSecurityPolicy.
Special notes for your reviewer:
The master change was added across a number of commits that moved the file around, so rather than cherrypicking each commit individually, I only grabbed the end-result. See https://github.com/kubernetes/kubernetes/tree/master/cluster/addons/metadata-agent/stackdriver/podsecuritypolicies
Does this PR introduce a user-facing change?:
/sig gcp
/assign @davidebelloni @kawych @foxish