Add timestamp annotation in tidbcluster statefulset (#1875) #1883
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.
cherry-pick #1875 to release-1.1
What problem does this PR solve?
fixes #1846
When
.Values.admission.validation.pods
is enabled, the process of upgrading and scaling for pd and tikv would be controlled by the admission webhook.And the admission webhook would face the problem that, as webhook would deny the request for deleting the pod if the tikv or the pd is not ready to be deleted, the interval duration between each 2 deleting request from sts controller would be much longer. This would cause the timeout error in our CI test. This request is to add the timestamp in each syncing in sts annotations to avoid this problem by adding the tidbcluster sts into the sts controller queue.
Does this PR introduce a user-facing change?: