kube-up to kops replacement blockers

[upodroid]

List of issues blocking kops from replacing kube-up e2e clusters

Beta Give feedback

1. Configure GCP Kubelet Credentials Provider #15974
   approved area/api area/documentation area/nodeup cncf-cla: yes lgtm size/L +7
   
2. GCP CCM should publish the correct release artifacts #15977
   blocks-next kind/feature lifecycle/rotten priority/important-soon +4
3. Add missing kube api-server config for alpha tests #15982
   cncf-cla: yes lifecycle/rotten needs-rebase size/M +4
   
4. Fix COS image mounter URL #15907
   approved area/nodeup cncf-cla: yes lgtm size/XS +5
   
5. Fix e2e testing logic #15900
   approved cncf-cla: yes lgtm size/M +4
   
6. Remove metadata-proxy from GCE Clusters from 1.29+ onwards #15885
   approved area/api area/documentation cncf-cla: yes lgtm size/L +6
   
7. Create a temporary staging bucket for kops builds #15981
   approved area/api cncf-cla: yes lgtm size/M +5
   
8. Expose port 22 on the API Server's Loadbalancer #15985
   kind/bug lifecycle/rotten +2
9. Configure ginkgo to use the KUBE_BASTION_SSH env variable #16008
   area/provider/gcp cncf-cla: yes lifecycle/rotten needs-rebase size/XXL +5
10. Build Kubernetes from source #16018
    approved cncf-cla: yes kind/office-hours lgtm size/XXL +5
    
11. Enable containerd test-handler runtimeclass for k/k e2e tests #16056
    approved area/api area/nodeup cncf-cla: yes lgtm size/S +6
    
12. Add --node-instance-group flag to ginkgo #16065
    approved area/provider/gcp cncf-cla: yes lgtm size/L +5
    
13. Add GCE scale testing on kops #16181
    approved area/addons area/provider/gcp cncf-cla: yes lgtm size/L +6
    
14. Add boskos-resource-type flag to use different GCE projects for scale/gpu testing #16268
    approved cncf-cla: yes lgtm size/M +4
    

Part of kubernetes/enhancements#4224

[upodroid]

/kind feature

[k8s-triage-robot]

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]

/remove-lifecycle stale
/priority important-soon

[k8s-triage-robot]

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]

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