Improved pod security #748
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Are there any backward compatibility issues that you know off of hand? |
|
I believe the seccompProfile only works on Kubernetes 1.19 and newer, at least that's when it became stable in docs. https://kubernetes.io/docs/tutorials/security/seccomp/ |
|
Cool. 1.19 is already EOL so we're good. |
|
@johrstrom Could we get this into 2.0.x release so I can remove some temporary exclusions in our policies? |
|
Sure thing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using Kyverno 1.6.0 pod security standards that mimic Kubernetes pod security standards. We do have to filter out a few that simply can't support, like we do have to allow hostPath, but these are simple security changes to be able to conform to these new policies.
┆Issue is synchronized with this Asana task by Unito