Allow passthrough of securityContext.readOnlyRootFilesystem in Helm chart#43332
Open
tnichols89 wants to merge 2 commits intofleetdm:mainfrom
Open
Allow passthrough of securityContext.readOnlyRootFilesystem in Helm chart#43332tnichols89 wants to merge 2 commits intofleetdm:mainfrom
tnichols89 wants to merge 2 commits intofleetdm:mainfrom
Conversation
tnichols89
requested review from
BCTBB,
ddribeiro,
georgekarrv,
ksatter and
rfairburn
as code owners
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
2 tasks
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
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.
Issue
Closes #43330
Description
This PR allows self-hosted, Kubernetes-based Fleet users to configure
securityContext.readOnlyRootFilesysteminvalues.yaml, which is then propagated down to thedeployment.yamltemplate.This change provides a convenient mechanism for users to fix a known issue while preserving the current default behavior.
Testing
The underlying
deployment.yamlchange has been tested in a standard Google Kubernetes Engine cluster, and is confirmed to fix the linked issue when using either Ubuntu-based or Container-Optimized OS (COS)-basedcontainerdcontainer runtimes in GKE.