Add Restricted-compatible security contexts - #139
Closed
unixfg wants to merge 1 commit into
Closed
Conversation
This file contains hidden or 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
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.
Summary
Rationale
The webhook already supports the unprivileged 8443 listener. These defaults make that deployment satisfy Kubernetes Pod Security Restricted while preserving the image's existing non-root UID. Both maps remain configurable, and setting either value to null omits that security context for installations with a different runtime contract.
Files changed
Validation
No DNSimple credentials or Kubernetes Secret contents were accessed or changed while preparing this contribution. A chart version bump is intentionally left to the repository's release workflow.