fix: skip revision injection when pod matched UpdateStrategy.Selector #1503
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.
Ⅰ. Describe what this PR does
This pull request aims to address the issue of revision injection for pods that match the upgrade policy. Currently, if a pod that has already been upgrade is recreated due to machine or pod failure, it will rollback to the old revision, leading to a false-positive release observation. This PR proposes a fix by implementing comments (
kruise/apis/apps/v1alpha1/sidecarset_types.go
Lines 226 to 228 in 5421ee7
Ⅱ. Does this pull request fix one issue?
Ⅲ. Describe how to verify it
unit test and manually.
Ⅳ. Special notes for reviews