fix: set resource Status using patch instead of update #6
Conversation
This file contains 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
Signed-off-by: PINCHON Benjamin <benjamin.pinchon@orange.com>
Signed-off-by: PINCHON Benjamin <benjamin.pinchon@orange.com>
mydoomfr
force-pushed
the
fix/patch-status
branch
from
c468e93 to
5faf1f6
Compare
Signed-off-by: PINCHON Benjamin <benjamin.pinchon@orange.com>
antrema
approved these changes
Aug 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Resource .Status should be updated using Patch() instead of Update().
Also, if a conflict is detected, it means the original object has been changed in etcd and we're working on an outdated object. So, it's probably better to requeue the reconciliation.