Always set AllBeta with AllAlpha for alpha CI jobs

[tallclair]

kubernetes/kubernetes#133697 adds the concept of feature-gate dependencies, and forbids enabling features with disabled dependencies. This means that if an Alpha feature depends on an off-by-default Beta, then enabling AllAlpha features on their own will fail. See summary of discussion here: kubernetes/kubernetes#133697 (comment)

To avoid breaking our alpha CI jobs, anywhere that AllAlpha is enabled, we should also enable AllBeta. In the case of ci-kubernetes-e2e-kind-alpha-features the job was removed because there is already a similar job that enables AllAlpha and AllBeta.

/cc @BenTheElder @pohly @aojea @liggitt

[SergeyKanzhelev]

/lgtm

[aojea]

It turned out to be used in more places than I expected

/lgtm
/approve

holding for others to chime in and have more eyes in case some jobs break with the change
/hold

[pohly]

/lgtm

My own removal PR is a subset of this one here. It got stuck on a discussion on other next steps. Let's merge this one here, then I'll update mine to do those next steps.

[tallclair]

My own removal PR is a subset of this one here. It got stuck on a discussion on other next steps. Let's merge this one here, then I'll update mine to do those next steps.

Ah, sorry, I missed that you'd already started on this. Thanks.

[BenTheElder]

/lgtm
/approve
/hold cancel

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aojea, BenTheElder, pohly, SergeyKanzhelev, tallclair

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• config/OWNERS [BenTheElder,aojea]
• releng/OWNERS [BenTheElder,aojea]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

@tallclair: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key cloud-provider-ibmcloud-ppc64le-periodics.yaml using file config/jobs/kubernetes/cloud-provider-ibmcloud/cloud-provider-ibmcloud-ppc64le-periodics.yaml
• key generated.yaml using file config/jobs/kubernetes/generated/generated.yaml
• key kops-periodics-misc2.yaml using file config/jobs/kubernetes/kops/kops-periodics-misc2.yaml
• key gcp-gce.yaml using file config/jobs/kubernetes/sig-cloud-provider/gcp/gcp-gce.yaml
• key periodic-e2e.yaml using file config/jobs/kubernetes/sig-cloud-provider/periodic-e2e.yaml
• key node-kubelet.yaml using file config/jobs/kubernetes/sig-node/node-kubelet.yaml
• key sig-node-presubmit.yaml using file config/jobs/kubernetes/sig-node/sig-node-presubmit.yaml
• key kubernetes-kind-ci.yaml using file config/jobs/kubernetes/sig-testing/kubernetes-kind-ci.yaml
• key kubernetes-kind-presubmits.yaml using file config/jobs/kubernetes/sig-testing/kubernetes-kind-presubmits.yaml

In response to this:

kubernetes/kubernetes#133697 adds the concept of feature-gate dependencies, and forbids enabling features with disabled dependencies. This means that if an Alpha feature depends on an off-by-default Beta, then enabling AllAlpha features on their own will fail. See summary of discussion here: kubernetes/kubernetes#133697 (comment)

To avoid breaking our alpha CI jobs, anywhere that AllAlpha is enabled, we should also enable AllBeta. In the case of ci-kubernetes-e2e-kind-alpha-features the job was removed because there is already a similar job that enables AllAlpha and AllBeta.

/cc @BenTheElder @pohly @aojea @liggitt

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.