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
helm chart: add container security context #3350
base: master
Are you sure you want to change the base?
Conversation
this change adds container security context support which might be required in some restricted environments Signed-off-by: viktoriaas <viktoria.spisakovaa@gmail.com>
Signed-off-by: viktoriaas <viktoria.spisakovaa@gmail.com>
@Monokaix opening a new PR featuring the same commits as before to maintain the history. |
/assign @hzxuzhonghu |
/lgtm |
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: william-wang 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 |
@viktoriaas please rebase and squash commits to only one. |
@viktoriaas: PR needs rebase. 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. |
This change adds container security context to admission, controller, scheduler Deployments, and scheduler Job. Container security context is necessary in some restricted environments, e.g. in an environment that employs Restricted Pod Security Standard as default.
This PR is just a cleaner version of #3322