Combine Operator CRDs and Operator Helm Chart into a Single Chart
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 300
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 184
Description
Now we have a better and more reliable release process that is tied to the same version. We can do away with the separate Helm Chart for Operator CRDs. We have now fixed the issue where CRDs weren't being upgraded through the chart releases and we can now remove the need for a separate CRDs helm chart but packaging the CRDs into the same chart as the Operator.
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 Operator Helm chart, the separate Operator CRDs Helm chart, and the release process described in the issue. Done means the CRDs are packaged in the Operator chart and the separate CRD chart is no longer needed, with releases remaining tied to the same version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100