pingcap / pingcap/tidb-operator
Use generic helm values to deploy tidb-operator in e2e
Open
Nobody has claimed this yet.
status/help-wanted
test/e2e
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Feature Request
Simple to use. We can focus on plain helm values and remove the OperatorConfig abstract level.
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 locating the e2e deployment configuration, the Helm values it uses, and references to the OperatorConfig abstraction. Determine how generic Helm values could replace that layer; done means tidb-operator deploys successfully in e2e without OperatorConfig and the relevant deployment checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100