kubernetes-sigs / kubernetes-sigs/crdify
Handling of new CRDs
Open
- Dominant language
- Go
- Stars
- 47
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
Could we add a flag to say the command should not fail if the old crd (in the cluster in my case) does not exist?
Contributor guide
Research direction
Start by locating the CLI command that compares CustomResourceDefinitions and its existing flag handling; no specific files or tests are named in the issue. Reproduce the comparison with a missing old CRD, then verify that the new flag allows the command to continue while the default behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100