-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
[WIP] Add Kubernetes Hardening Guide #37165
Conversation
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
/sig security |
Co-authored-by: Zak Scholl <[email protected]>
57ec28f
to
9146a5e
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@cailynse, how can we help you move this work forward? |
Hello @cailynse , checking in. Is there anything we can do to help here? |
Hi @divya-mohan0209 - sorry, been swamped with a few other things. I'll work. on breaking this down more clearly this week so it's easier for folks to contribute. |
After some discussion we have decided to create separate pages for the sections of the hardening guide. I will close this PR as we will open separate PRs for each section to make it easier for folks to pick up a specific section. |
Addresses issue kubernetes/sig-security#30 in k/sig-security repository.
This is a draft for the Kubernetes Hardening Guide from the collaborative document. There are still lots of areas that need to be fleshed out before this PR is ready for review.