Set security context run as user and group from pod annotations #17
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
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.
This is a similar situation as #12 was done to address. Specifically, there are deployments that set the pod security context (https://kubernetes.io/docs/tasks/configure-pod-container/security-context/) which overrides the UID and GID of the running container. When this is done the
iptablesacceptrule created by https://github.com/qpoint-io/kubernetes-qtap-init/ doesn't align and then prevents the sidecar proxy from using the network. This is due to the fact that the the sidecar ends up being configured to route to itself and this breaks registration and pretty much any network connectivity since the sidecar container cannot become healthy.