-
Notifications
You must be signed in to change notification settings - Fork 499
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove the PodRestarter controller and tidb.pingcap.com/pod-defer-deleting
annotation
#3296
Conversation
Signed-off-by: Lonng <[email protected]>
Signed-off-by: Lonng <[email protected]>
Signed-off-by: Lonng <[email protected]>
Codecov Report
@@ Coverage Diff @@
## master #3296 +/- ##
==========================================
+ Coverage 39.76% 42.33% +2.57%
==========================================
Files 172 159 -13
Lines 17558 16371 -1187
==========================================
- Hits 6982 6931 -51
+ Misses 9925 8802 -1123
+ Partials 651 638 -13
Flags with carried forward coverage won't be shown. Click here to find out more. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: ti-srebot <[email protected]>
cherry pick to release-1.0 in PR #3300 |
Signed-off-by: ti-srebot <[email protected]>
cherry pick to release-1.1 in PR #3301 |
…leting` annotation (pingcap#3296) Signed-off-by: Lonng <[email protected]>
…leting` annotation (#3296) (#3301) Signed-off-by: Lonng <[email protected]> Co-authored-by: Lonng <[email protected]>
…leting` annotation (pingcap#3296) Signed-off-by: Lonng <[email protected]>
What problem does this PR solve?
This
PodRestarter
is used to restart a pod by annotating it withtidb.pingcap.com/pod-defer-deleting
. However, there is no user to use this feature because we recommandate users to restart pods gracefully via instrucations https://docs.pingcap.com/tidb-in-kubernetes/dev/restart-a-tidb-cluster#performing-a-graceful-rolling-restart-to-all-pods-in-a-component. ThePodRestarter
control will retrieve all pods belongs to the current TiDBCluster instance when everysync
iteration and delete some of it, I think there is unnecessary cost.What is changed and how does it work?
Remove the
PodRestarter
Check List
Tests
Code changes
Does this PR introduce a user-facing change?: