pingcap / pingcap/tidb-operator
How to deploy TiKV only?
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Question
I would like to try out SurrealDB. They have a TiKV backend, so obviously I would search for TiKV operator, but that is dead and I was redirected here, but so far I did not find any options to disable TiDB.
I don't TiDB because I don't use MySQL. It is unnecessary so it is best to remove it
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 file, test, or entry point is named in the issue. Start by reviewing the TiDB Operator's cluster deployment configuration and how it provisions TiDB and TiKV. Done should be a supported, documented way to run TiKV without deploying TiDB, with validation for the resulting cluster configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100