Promoting kind alpha/beta features jobs to Release Blocking

[BenTheElder]

What would you like to be added:

We should promote these three jobs to release blocking from release informing:

1. ci-kubernetes-e2e-kind-alpha-beta-features

• https://testgrid.k8s.io/sig-release-master-informing#kind-master-alpha-beta
• https://prow.k8s.io/?job=ci-kubernetes-e2e-kind-alpha-beta-features

2. ci-kubernetes-e2e-kind-alpha-features

• https://testgrid.k8s.io/sig-release-master-informing#kind-master-alpha
• https://prow.k8s.io/?job=ci-kubernetes-e2e-kind-alpha-features

3. ci-kubernetes-e2e-kind-beta-features

• https://testgrid.k8s.io/sig-release-master-informing#kind-master-beta
• https://prow.k8s.io/?job=ci-kubernetes-e2e-kind-beta-features

Why is this needed:

These jobs are stable and have caught real regressions like this one where the api server no longer starts with alpha features enabled.

They run a subset of e2e tests with alpha + beta + GA, alpha + GA, and beta +GA enabled respectively.

@aojea and I have been keeping an eye on these.

This issue is part of the process at https://github.com/kubernetes/sig-release/blob/master/release-blocking-jobs.md#promoting-or-demoting-jobs

[BenTheElder]

mailinglist notice at https://groups.google.com/a/kubernetes.io/g/dev/c/k0KQVbuJg0E

[aojea]

+1

[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

[BenTheElder]

I have been thinking about this, I actually think our top priority should be to get beta feature testing into blocking + PR blocking to align with kubernetes/enhancements#5242

We should consider substituting the PR job for the ipv6 PR job that we probably don't need. We should make sure IPv6 is release blocking though.

[BenTheElder]

/remove-lifecycle stale