pingcap / pingcap/tidb-operator
Manage TiCDC replication tasks in CRD
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Feature Request
Is your feature request related to a problem? Please describe:
Today, after deploying ticdc using tidb-operator it's necessary to manually manage replication tasks using the cdc CLI. This doesn't fit very well with the approach used by Kubernetes users to manage their resources.
Describe the feature you'd like:
It would be nice to be able to define a TiCDC replication task in a CRD and have tidb-operator manage the task.
Describe alternatives you've considered:
Teachability, Documentation, Adoption, Migration Strategy:
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
Start by reviewing the existing Kubernetes CRDs and how tidb-operator currently integrates with TiCDC. Define what a replication-task CRD should represent and how the operator would manage it instead of manual cdc CLI commands; completion requires an agreed API and lifecycle behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- distributed-systems, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100