[bitnami/sealed-secrets] Fix namespace in PodDisruptionBudget #30453
+8
−4
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.
Description of the change
Currently the PodDisruptionBudget in the sealed-secret chart is deployed to the release namespace. This however, is not necessarily the namespace the rest of the sealed-secrets manifests are deployed to (i.e. due to
.Values.namespaceOverride
being set).That leads to a violated PodDisruptionBudget in the release namespace, as the pods it references are deployed to a different namespace.
This PR updates the namespace field in the PDB to have the same value as for example the deployment it references:
Benefits
Setting
.Values.namespaceOverride
no longer breaks the PDB.Checklist
Chart.yaml
according to semver. This is not necessary when the changes only affect README.md files.