Fix duplicate Prom configmap reloader securitycontext #2930
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.
Signed-off-by: chipzoller chipzoller@gmail.com
What does this PR change?
Removes a redundant if clause and fixes a duplicate securityContext entry in Prometheus' configmap reloader container.
Does this PR rely on any other PRs?
No, but these changes may be obviated if the intention in 2.0 is to remove the configmap reloader, in which case this is throw-away work.
How does this PR impact users? (This is the kind of thing that goes in release notes!)
Allows Prometheus to deploy correctly if the global level containerSecurityContext is not defined (not default).
Links to Issues or tickets this PR addresses or fixes
Fixes #2926
What risks are associated with merging this PR? What is required to fully test this PR?
May still deploy incorrectly.
How was this PR tested?
Helm templating with various settings.
Have you made an update to documentation? If so, please provide the corresponding PR.
N/A