Add troubleshooting entry for rollback missing resource error#2056
Open
promptless-for-oss wants to merge 12 commits intohelm:mainfrom
Open
Add troubleshooting entry for rollback missing resource error#2056promptless-for-oss wants to merge 12 commits intohelm:mainfrom
promptless-for-oss wants to merge 12 commits intohelm:mainfrom
Conversation
Document the scenario where helm rollback fails with "no [Resource] with the name '[name]' found" when a failed upgrade leaves resources on the cluster that are missing from the original release metadata. This issue is fixed in newer Helm 3 releases.
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.
Documents the scenario where
helm rollbackfails with "no [Resource] with the name '[name]' found" when a failed upgrade leaves resources on the cluster that are missing from the original release metadata. Explains the specific sequence of events that triggers this issue and notes that it is fixed in newer Helm 3 releases.