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

Enabling or disabling TLS on existing clusters managed by the tidb-operator #5700

Open
snowballbear opened this issue Aug 2, 2024 · 2 comments

Comments

@snowballbear
Copy link

Feature Request

Currently, enabling or disabling TLS is not supported for existing clusters managed by TiDB Operator. This feature can only be enabled during cluster creation. For existing clusters, the only way to enable or disable TLS is by rebuilding the cluster, which is very inconvenient. It is recommended to add support for enabling or disabling TLS on existing clusters.

@csuzhangxc
Copy link
Member

Another method to enable/disable TLS on existing clusters is: suspend the cluster -> update TLS config -> resume the cluster.

This can't be done with a rolling update as during the updating, some components with TLS but some without, then they can't talk to each other.

@csuzhangxc
Copy link
Member

csuzhangxc commented Aug 8, 2024

Another method to enable/disable TLS on existing clusters is: suspend the cluster -> update TLS config -> resume the cluster.

This can't be done with a rolling update as during the updating, some components with TLS but some without, then they can't talk to each other.

Sorry, we tested this method, but it doesn't work as the Peer URL of PD can't be updated from http to https.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants