fix: Revert setting storage class fields to null by default [RHIDP-5953]
#97
Conversation
When the PVC is initially created, it gets assigned the default storage class And it becomes impossible to upgrade the Helm Release later on because it looks like the (immutable) PVC is being patched after creation
rm3l
changed the title
null by defaultnull by default
rm3l
changed the title
null by defaultnull by default [RHIDP-5953]
|
/cherry-pick release-1.5 |
|
@rm3l: once the present PR merges, I will cherry-pick it on top of In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
rm3l
changed the title
null by default [RHIDP-5953]null by default [RHIDP-5953]
…s previous version When using the '–upgrade' flag, regression testing will only be performed if the major version of the Chart is not changed (Semver). Otherwise, normal testing will still happen.
|
|
@rm3l: new pull request created: #100 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Description of the change
When the DB PVC is initially created, it gets assigned the default storage class.
And it becomes impossible to upgrade the Helm Release later on because it looks like the (immutable) PVC is being patched after creation
Existing or Associated Issue(s)
Relates to https://issues.redhat.com/browse/RHIDP-5953
Additional Information
Checklist
Chart.yamlaccording to semver.values.yamland added to the README.md. The pre-commit utility can be used to generate the necessary content. Usepre-commit run -ato apply changes.pre-commithook.ct lintcommand.