Devops 650 allow multiple updates of same resource #16
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.
We have changed the way updates are done.
Until now, when the Redis statefulset was updated, it waited until the rolling update to be finished. The same happened with Sentinel with its deployment.
He have multiple premises in mind:
So, from now, the updates don't wait to themselves to be finished. In stead, they check that the other resource is ready and there's no an update being done (to prevent simultaneous redis and sentinel updates).