Separately publish CRD.yaml in relases
Open
Nobody has claimed this yet.
kind/bug
lifecycle/frozen
triage/wg-discuss
- Dominant language
- Go
- Stars
- 608
- Forks
- 263
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 125
Description
For installing the Helm chart and CRDs separately, it would be super useful to have separate openshift-crds.yaml and kubernetes-crds.yaml files attached to the Github releases.
It should be fairly simply to extract these manifests when generating the kustomize manifests during the release process.
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
Inspect the release process that generates the kustomize manifests and the GitHub release configuration. Produce separate openshift-crds.yaml and kubernetes-crds.yaml artifacts for the Helm chart installation workflow, then verify that both files are attached to a release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100