Promoting kind beta, alpha, alpha+beta features jobs to Release Blocking

[Benjamin Elder]

Tracking Issue: https://github.com/kubernetes/sig-release/issues/2740

I propose promoting these jobs from release informing to release blocking, they've been stable and caught real regressions (including recently the inability to start kube-apiserver when alpha features are enabled). Antonio and I are monitoring these and other than Kubernetes regressions they have been reliable.

We currently have only one alpha features job in release blocking (which did not catch the recent regression) and no beta-features jobs (other than implicit coverage of default-enabled features, which has not included all betas). 

https://testgrid.k8s.io/sig-release-master-blocking#gce-cos-master-alpha-features

Thank you to Antonio for developing and shepherding these jobs 🙏

- Ben

[Davanum Srinivas]

+1 from me

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-re...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/kubernetes-sig-release/CAOZRXm_y9QE8LRHEm6%2BTjzirfeZqiSiqUxsR2eBnimzJtiMCXw%40mail.gmail.com.

--

Davanum Srinivas :: https://twitter.com/dims

[Patrick Ohly]

"'Benjamin Elder' via kubernetes-sig-testing"

<kubernetes-...@googlegroups.com> writes:
> Tracking Issue: https://github.com/kubernetes/sig-release/issues/2740
>
> I propose promoting these jobs from release informing to release
> blocking,

+1 from me.
--
Best Regards

Patrick Ohly
Cloud Software Architect

[Benjamin Elder]

After some discussion in SIG Testing [^1], we think we should only promote beta to release blocking, and keep alpha-features-enabled as informing.

We also think we should clearly distinguish "alpha/beta enabled cluster is tested" vs "alpha/beta tests are tested", and that "alpha tests are tested" should not even be release-informing, instead only "informing" feature promotion PRs.

We will circle back with an updated job promotion proposal when the jobs and tooling have been updated to reflect this and are proven stable.

Let's pause this for now while we revamp test tagging and the jobs:
https://groups.google.com/g/kubernetes-sig-testing/c/-qsyL_H3f7M

Thanks all
- Ben

[^1]: https://kubernetes.slack.com/archives/C09QZ4DQB/p1741974517038949

On Mon, Mar 3, 2025 at 11:51 AM Carlos Tadeu Panato Jr <cta...@gmail.com> wrote:

+1

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-testing" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-te...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/kubernetes-sig-testing/yrjh5xkq0vv8.fsf%40pohly-mobl1.fritz.box.