Use StatefulSet status instead of List Pod by selector labels #228
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.
I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
Pull request type
Please check the type of change your PR introduces:
What is the current behavior?
After changes from PR #172 controllers are waiting for recreating pods with new label
ydb.tech/statefulset-name
. WIthstrategyUpdate: OnDelete
policy usage it affect controllers by infinite loop for pods create by old generation of StatefulSet.What is the new behavior?
waitForStatefulSetToScale
ydb.tech/remote-cluster
label in StatefulSet builder for Nodeset objectsOther information