kops icon indicating copy to clipboard operation
kops copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes

kube-up to kops replacement blockers

Open upodroid opened this issue 2 years ago • 5 comments 

### 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 avatar Oct 02 '23 11:10 upodroid

/kind feature

upodroid avatar Oct 02 '23 11:10 upodroid

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 avatar Jan 31 '24 06:01 k8s-triage-robot

/remove-lifecycle stale /priority important-soon

upodroid avatar Jan 31 '24 12:01 upodroid

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 avatar Apr 30 '24 13:04 k8s-triage-robot

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

k8s-triage-robot avatar May 30 '24 13:05 k8s-triage-robot