pingcap / pingcap/tidb-operator
Move crds define to operator
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Like spark operator write by google team:
https://github.com/GoogleCloudPlatform/spark-on-k8s-operator/tree/master/charts/spark-operator-chart
You could found crds define in the charts path. It is humanize when use pulumi define app project.
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
Compare the Google spark-on-k8s-operator chart linked in the issue, then locate the CRD definitions in this repository's charts path. Trace how the operator currently defines or installs them and how a Pulumi app project would consume them. Done means the CRDs are provided from the operator in a way that supports that workflow and existing deployment behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100