feat(deploy) Allow setting additional values in operator chart #1904
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
…rityContext/securityContext in operator chart Signed-off-by: bakito <github@bakito.ch>
rksharma95
force-pushed
the
extend-helm-chart
branch
from
51e3a0c to
3110da7
Compare
rksharma95
approved these changes
Jan 2, 2025
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.
Purpose of PR?:
This PR allows defining adidional values in the operator helm chart. (resources/podLabels/podAnnotations/podSecurityContext/securityContext)
Fixes -
Does this PR introduce a breaking change?
no
If the changes in this PR are manually verified, list down the scenarios covered::
Installed helm chart without and with new values
Additional information for reviewer? :
Checklist:
<type>(<scope>): <subject>