This repository was archived by the owner on Jun 8, 2022. It is now read-only.
Open
Conversation
Signed-off-by: Daniel Higuero <daniel@napptive.com>
dhiguero
force-pushed
the
feature/security_context
branch
from
faecdb3 to
e992068
Compare
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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 PR adds support for specifying a security context on the ContainerizedWorkload.
This addresses an issue we found when deploying application on a Kubernetes cluster that enforces
PodSecurityPolicy. Without this change some applications may fail to start, as Kubernetes will complain about the security context of the resulting application. The proposed change is based on the existingcorev1.SecurityContextfrom Kubernetes limiting the scope to options that are only related with the container itself, and not with Kubernetes/Framework dependent options.