Including securityContext as configurable options with defaults set. #4894
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.
Tracking issue
#4893
Closes #4893
Why are the changes needed?
Without chart modifications, we are unable to deploy the flyte-core chart into OpenShift environments or other k8s environments that do not allow specification of user IDs.
What changes were proposed in this pull request?
Adds ability to override securityContext in Helm chart deployment for flyteadmin, flyteconsole, datacatalog, flytepropeller, and flytescheduler.
How was this patch tested?
Deployed in an on-prem environment.
Setup process
Screenshots
Check all the applicable boxes