kube-up to kops replacement blockers
- Dominant language
- Go
- Stars
- 16.7k
- Forks
- 4.7k
- Avg merge
- 17h 21m
- Merged PRs (30d)
- 68
Description
```[tasklist]
### List of issues blocking kops from replacing kube-up e2e clusters
- [ ] #15974
- [ ] https://github.com/kubernetes/kops/issues/15977
- [ ] https://github.com/kubernetes/kops/pull/15982
- [ ] https://github.com/kubernetes/kops/pull/15907
- [ ] https://github.com/kubernetes/kops/pull/15900
- [ ] https://github.com/kubernetes/kops/pull/15885
- [ ] https://github.com/kubernetes/kops/pull/15981
- [ ] https://github.com/kubernetes/kops/issues/15985
- [ ] https://github.com/kubernetes/kops/pull/16008
- [ ] https://github.com/kubernetes/kops/pull/16018
- [ ] https://github.com/kubernetes/kops/pull/16056
- [ ] https://github.com/kubernetes/kops/pull/16065
- [ ] https://github.com/kubernetes/kops/pull/16181
- [ ] https://github.com/kubernetes/kops/pull/16268
```
Part of https://github.com/kubernetes/enhancements/issues/4224
Contributor guide
Research direction
Start by reviewing the linked blocking issue #15974, issue #15977, and the referenced pull requests, then read Kubernetes enhancements issue #4224 for the broader replacement plan. This issue is a tracking list rather than a standalone implementation task; it is done when the listed kube-up replacement blockers are resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100