Skip to content
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

Support enable or disable TLS for an exiting cluster #1598

Closed
qqqdan opened this issue Oct 26, 2021 · 1 comment · Fixed by #1657
Closed

Support enable or disable TLS for an exiting cluster #1598

qqqdan opened this issue Oct 26, 2021 · 1 comment · Fixed by #1657
Assignees
Labels
type/feature-request Categorizes issue as related to a new feature.
Milestone

Comments

@qqqdan
Copy link
Collaborator

qqqdan commented Oct 26, 2021

Feature Request

Is your feature request related to a problem? Please describe:

This feature is from a customer with 30+ v4.0+ tidb clusters.
They need to enable TLS for these clusters, and currently tiup does not support the enable action.

Describe the feature you'd like:

In #673 ,we supported deploying a new cluster with TLS.
We need also support enable or disable TLS for existing cluster. Customer can accept that TiDB will stop during the enable/disable process.

Why the featue is needed:

Customer needs this feature.

Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:

@qqqdan qqqdan added the type/feature-request Categorizes issue as related to a new feature. label Oct 26, 2021
@qqqdan qqqdan added this to the v1.8.0 milestone Oct 26, 2021
@srstack srstack self-assigned this Nov 18, 2021
@srstack
Copy link
Collaborator

srstack commented Nov 20, 2021

  1. tiup cluster stl enable/disable [--skip-restart] # default restart the cluster
  2. tiup cluster restart

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/feature-request Categorizes issue as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants