Fix or reduce frequency or switch off perma-failing jobs

[dims]

Data as of June 3rd, 9:00 PM Eastern. Latest data can be found here:
http://storage.googleapis.com/k8s-metrics/failures-latest.json

CI Job	Days Failed
e2e-kops-aws-cni-calico-ipv6	32
e2e-kops-aws-cni-calico-ipv6-flatcar	32
e2e-kops-aws-cni-cilium-ipv6	32
e2e-kops-aws-external-dns	32
e2e-kops-aws-ipv6-external-dns	4
e2e-kops-aws-ipv6-flatcar	32
e2e-kops-aws-ipv6-karpenter	196
e2e-kops-aws-karpenter	93
e2e-kops-gce-latest	32
e2e-kops-gce-leader-migration	175
e2e-kops-gce-stable	73
e2e-kops-grid-cilium-deb10-k25-ko25	33
e2e-kops-grid-cilium-eni-amzn2-k23	187
e2e-kops-grid-cilium-eni-amzn2-k23-ko26	155
e2e-kops-grid-cilium-eni-amzn2-k24-ko26	162
e2e-kops-grid-cilium-eni-amzn2-k25	193
e2e-kops-grid-cilium-eni-amzn2-k25-ko26	159
e2e-kops-grid-cilium-eni-amzn2-k26	171
e2e-kops-grid-cilium-eni-amzn2-k26-ko26	156
e2e-kops-grid-cilium-eni-flatcar-k23	72
e2e-kops-grid-cilium-eni-flatcar-k23-ko26	43
e2e-kops-grid-cilium-eni-flatcar-k24-ko26	33
e2e-kops-grid-cilium-eni-flatcar-k25-ko26	45
e2e-kops-grid-cilium-eni-rhel8-k23	193
e2e-kops-grid-cilium-eni-rhel8-k23-ko26	161
e2e-kops-grid-cilium-eni-rhel8-k24	191
e2e-kops-grid-cilium-eni-rhel8-k25	187
e2e-kops-grid-cilium-eni-rhel8-k25-ko26	157
e2e-kops-grid-cilium-eni-rhel8-k26-ko26	161
e2e-kops-grid-gce-cilium-u2004-k23	175
e2e-kops-scenario-arm64	33
e2e-kops-scenario-ipv6-terraform	33
e2e-kops-scenario-no-irsa	32
e2e-kops-scenario-terraform	32
e2e-kops-warm-pool	110
pull-kops-e2e-aws-upgrade-k123-ko125-to-k124-kolatest-karpenter	88

/kind bug

[dims]

cc @justinsb

[pacoxu]

https://prow.k8s.io/job-history/gs/kubernetes-jenkins/logs/e2e-kops-grid-cilium-eni-u2004-k26 keeps failing after Oct 26. Not sure if this is the right place to raise.

[justinsb]

We reviewed the latest "set" of failures in kOps office hours and identified two common causes for a set of failures that started 30 days ago. (Ginkgo moving from v1 -> v2; deletion of the updown jobs for kOps 1.26). We're going to remove any remaining kube 1.24 and kOps 1.26 jobs, as those are no longer supported.

Then we can see where we are in terms of other (perhaps more real) failures.

[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

[rifelpet]

There is still more triaging to do

/remove-lifecycle stale

[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