CRD API v2
Open
kind/feature
status/never-stale
- Dominant language
- Go
- Stars
- 927
- Forks
- 387
- Avg merge
- 15h 5m
- Merged PRs (30d)
- 36
Description
### Requirement
When we have completed the rework of the 3.x we should be moving to a new stable CRD API as the older API will contain too many unused features that would make it complicated to use.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue provides no file, test, or entry point to begin with. First identify where the current CRD API is defined and how the 3.x rework is tracked; done requires an agreed stable CRD API v2 design that removes unused features.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- api, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100