fix: remove unstable selector labels in mssql and octopus statefulsets#540
fix: remove unstable selector labels in mssql and octopus statefulsets#540oleksandr-codefresh merged 6 commits intomainfrom
Conversation
🦋 Changeset detectedLatest commit: 853e3d1 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
…ix-sts-dynamic-selectors
| "helm.sh/hook": pre-upgrade | ||
| "helm.sh/hook-weight": "-5" | ||
| "helm.sh/hook-delete-policy": before-hook-creation,hook-succeeded | ||
| rules: |
There was a problem hiding this comment.
I would add a way to disable this hook (and the extra role/rolebinding/service account) since once the user upgrades and all the stateful sets are recreated with the correct labels, there is no longer need to run the hook.
There was a problem hiding this comment.
what default behaviour u suggest?
-
enabled: false- that makes things inconvenient, as requires user to read docs once meet issue and we don't know from which version to which they gonna update. -
enabled: true- I guess in most cases users also won't bother about having this extra value
There was a problem hiding this comment.
added
hooks:
enableSelectorLabelsFix: true
d9cadf9 to
f950d18
Compare
…x and corresponding tests
f950d18 to
853e3d1
Compare
Fixed issue
matchLabels(which is immutable) included labelhelm.sh/charthad dynamic value. That was preventing chart from upgrading