docs: add upgrading section covering manual CRD updates#264
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds an Upgrading section to the quick-start guide (linked from the README) documenting that
helm upgradedoes not update CRDs and they must be applied manually, with the exactkubectl apply --server-side -kcommand pinned to the release tag.Verified live: a cluster upgraded via
helm upgradealone keeps the old CRDs; the referenced int32 pipeline-hash issue reproduces on Kubernetes v1.36 with pre-v0.5.0 CRDs and is fixed once the updated CRDs are applied.