kube-up to kops replacement blockers

kubernetes / kops

Kubernetes Operations (kOps) - Production Grade k8s Installation, Upgrades and Management

https://kops.sigs.k8s.io/

Apache License 2.0

15.66k stars 4.61k forks source link

kube-up to kops replacement blockers #15983

Open upodroid opened 9 months ago

upodroid commented 9 months ago

### 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

upodroid commented 9 months ago

/kind feature

k8s-triage-robot commented 5 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

upodroid commented 5 months ago

/remove-lifecycle stale /priority important-soon

k8s-triage-robot commented 2 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 month ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten