Open
Conversation
Move the three-way merge patch examples from the Helm 2 vs 3 FAQ into a dedicated topics page. Add documentation for CRD/JSON merge patch fallback behavior and the --force flag. The FAQ retains the introductory explanation and cross-references the new page for details. Fixes helm#1448 Continues the work from helm#1473 Signed-off-by: kovan <xaum.io@gmail.com>
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.
Summary
topics/resource_upgrades.md--forceflag — explains it performs full resource replacement, not patching, with caveats about immutable fieldsFixes #1448
Continues the work from #1473 (by @gjenkins8, who noted the CRD/jsonpatch behavior should be documented but never returned to finish)
Test plan