-
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
chart: do not deploy tidb-scheduler by default #5458
Conversation
/run-all-tests |
/run-all-tests |
/run-all-tests |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #5458 +/- ##
===========================================
- Coverage 61.42% 47.52% -13.91%
===========================================
Files 230 214 -16
Lines 29152 29000 -152
===========================================
- Hits 17908 13783 -4125
- Misses 9483 13586 +4103
+ Partials 1761 1631 -130
|
/run-pull-e2e-kind |
1 similar comment
/run-pull-e2e-kind |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: z2665 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
What problem does this PR solve?
for k8s > v1.19, we often don't need to deploy tidb-scheduler. ref https://docs.pingcap.com/tidb-in-kubernetes/stable/tidb-scheduler
and some users became confused when deploying tidb-scheduler (e.g #5462), so we disable it by default from v1.6.
What is changed and how does it work?
Code changes
Tests
Side effects
Related changes
Release Notes
Please refer to Release Notes Language Style Guide before writing the release note.