-
Notifications
You must be signed in to change notification settings - Fork 14.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
Clarify init container use case for security #17404
Conversation
Deploy preview for kubernetes-io-master-staging ready! Built with commit 66f3873 https://deploy-preview-17404--kubernetes-io-master-staging.netlify.com |
/assign @sftim |
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.
/lgtm
/assign @cody-clark |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tengqm 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 |
Fixes #16686
Reasoning: This bullet point has lead to some confusion about how exactly it increases security. I believe it makes more sense to put it at the end of the bullet points list to introduce all concepts first, this makes it a little easier to follow. Second, clarify that running tools in your init containers reduces the attack surface of your application, introducing the clarity of why it makes your app more secure.