We might need to enforce "one version at a time" upgrade
Open
lifecycle/frozen
lifecycle/stale
- Dominant language
- Go
- Stars
- 16.7k
- Forks
- 4.7k
- Avg merge
- 17h 21m
- Merged PRs (30d)
- 68
Description
e.g. https://github.com/kubernetes/kubernetes/issues/47474
Contributor guide
Research direction
Start by reading the linked Kubernetes issue and tracing how kOps currently handles cluster upgrades. The issue does not name files, tests, or a concrete acceptance condition; clarify the one-version-at-a-time policy and define tests that demonstrate enforcement before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100