Use semantic versioning for CRD updates
- Dominant language
- Go
- Stars
- 283
- Forks
- 148
- PR merge metrics
- No merged PRs in 30d
Description
As an operator of a k8s cluster that supports creation of SolrCloud instances by others, I want to deploy multiple semantically-versioned CRDs in parallel so that I am able to support users of older versions of the Solr helm chart (or raw manifests) alongside users of more recent versions.
(The CRDs have all called themselves `v1beta1` for a while now, even as there have been breaking changes.)
Contributor guide
No contributing guide indexed for this repository
Research direction
No file or test paths are identified in the issue. Start by locating the CRD definitions and the Helm chart or raw manifests, then determine how multiple semantically versioned CRDs can coexist for older and newer Solr chart users. Done means parallel deployment supports both versions without breaking existing SolrCloud users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, helm, kubernetes
- Domain
- api, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100