This repository has been archived by the owner on Feb 22, 2022. It is now read-only.
[stable/mongodb] Fix 'storageClass' macros #16546
Merged
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: Alejandro Moreno amoreno@bitnami.com
What this PR does / why we need it:
At #16434 we introduced a new macro that allows us to use a
global.storageClass
parameter to overwrite any other storageClassName used on other parameters.Despite new PVCs and Statefulsets generated are syntactically correct (PVC manifests generate exactly the same PVC in the K8s cluster), we introduce a backwards incompatibility since Helm includes some "sanity checks" to ensure immutable objects do not change their specs during an upgrade (see the error below):
Error: UPGRADE FAILED: PersistentVolumeClaim "xxxxx" is invalid: spec: Forbidden: is immutable after creation except resources.requests for bound claims
This error is a consequence of the change below introduced in the PR (when no storagleClass is provided):
kind: PersistentVolumeClaim ... requests: storage: "8Gi" + storageClassName:
Checklist
[stable/chart]
)