Add SecurityContext configuration for Cleanup Job - #2187
Merged
TylerHelmuth merged 1 commit intoMay 7, 2026
Conversation
SecurityContext configuration is required to ensure the cleanup job can run in environments with restricted pod security admission
TylerHelmuth
approved these changes
May 7, 2026
10 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
2 participants
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.
As stated in issue #2186, current Cleanup Job does not allow to configure security context. In environments where Pod Security Admission (PSA) is set to restricted,
helm uninstallcommand timeouts due to the fact that the cleanup job is not able to start.This PR adds the possibility to specify a security context for the cleanup job, but does not change the default behavior. This means that as it stands, PSA would still prevent the cleanup job from starting. However, with the changes, a new
values.yamlvalue can be specified with the extra security context config that ensure that the job can meet the requirements in the restricted environment.