actions / actions/actions-runner-controller
Upgrade CRDs through kubectl apply -k
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 27
Description
What would you like added?
Add kustomization.yaml file into crds folder so we can run kubectl apply -k LINK to upgrade CRDs because Helm doesn't manage CRD resources.
Why is this needed?
It should be easier to update CRDs when we need
Additional context
Example from ArgoCD helm chart
https://artifacthub.io/packages/helm/argo/argo-cd#custom-resource-definitions
https://github.com/argoproj/argo-cd/blob/master/manifests/crds/kustomization.yaml
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 inspecting the repository's crds folder and compare its contents with the linked ArgoCD kustomization.yaml example. Add the requested kustomization.yaml so the CRDs can be consumed through kubectl apply -k LINK; done means the CRD directory is usable as a Kustomize target.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100