fix: chart crd forceUpgrade field should be nil by default #5068
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
Even though the
forceUpgrade
field is a nil pointer, the k8s controller seems to be setting the field automatically in CRs that exist once the CRD is updated via a k0s upgrade. I believe this is because it defaults to true via the generated openapi spec.This results in a backwards incompatible change for those importing the schema prior to this version.
Fixes # (issue)
Type of change
How Has This Been Tested?
To test for forward compatibility, install the latest k0s 1.30 release and see that it upgrades fine back to default: true.
Checklist: