pingcap / pingcap/tidb-operator
Enabling or disabling TLS on existing clusters managed by the tidb-operator
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by tracing how TLS is handled during cluster creation and how the operator reconciles existing clusters, then define the supported enable and disable transitions. Done should mean an existing managed cluster can change TLS state without rebuilding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100