add restrict-service-account sample policy #30
Merged
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.
Related to kyverno/kyverno#1619
I did a few tests and this approach seems straightforward to me - not sure if there are any gotchas. Notice that the first rule could be optional but in a real-world scenario, I'd like to have it in place to prevent that the pod could be created by a controller using the default service account. We may consider removing the first rule to keep the sample more concise. I'm intentionally leaving init containers out of scope.