Drop explicit ClusterTrustBundle focus from alpha-only jobs

[liggitt]

This is step 1 of transitioning ClusterTrustBundle from alpha to beta. Promotion from alpha to beta will turn these alpha-only jobs which explicitly focus on the ClusterTrustBundle tests red. It was questionable to structure these this way in the first place.

Step 2 will get these tests added to run in the kind-alpha / kind-alpha-beta jobs in a follow-up (will likely require both test-infra and k/k PRs).

Step 3 will promote CTB to beta and ensure that the tests run in the kind-alpha-beta / kind-beta jobs (will ideally only require a k/k PR).

cc @stlaz @pohly @aojea

context:

• ClusterTrustBundles - move to beta kubernetes#128499 (comment)
• always enable ClusterTrusbBundles feature gates in tests that both focus it and enable all alpha APIs #34451
• Shift generic alpha and beta jobs to generic alpha and beta feature tags #34456
• Switch cluster trust bundle e2e tests to feature-gate tagging kubernetes#130567
• WIP: POC of beta promotion with e2es kubernetes#130572
• e2e framework: add [Feature:Alpha] or [Feature:Beta] via WithFeatureGate kubernetes#130580

[stlaz]

/lgtm

[BenTheElder]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BenTheElder, liggitt

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/jobs/kubernetes/sig-cloud-provider/OWNERS [BenTheElder]
• config/jobs/kubernetes/sig-node/OWNERS [BenTheElder]
• releng/OWNERS [BenTheElder]

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]

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

• 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 sig-node-presubmit.yaml using file config/jobs/kubernetes/sig-node/sig-node-presubmit.yaml

In response to this:

This is step 1 of transitioning ClusterTrustBundle from alpha to beta. Promotion from alpha to beta will turn these alpha-only jobs which explicitly focus on the ClusterTrustBundle tests red. It was questionable to structure these this way in the first place.

Step 2 will get these tests added to run in the kind-alpha / kind-alpha-beta jobs in a follow-up (will likely require both test-infra and k/k PRs).

Step 3 will promote CTB to beta and ensure that the tests run in the kind-alpha-beta / kind-beta jobs (will ideally only require a k/k PR).

cc @stlaz @pohly @aojea

context:

• ClusterTrustBundles - move to beta kubernetes#128499 (comment)
• always enable ClusterTrusbBundles feature gates in tests that both focus it and enable all alpha APIs #34451
• Shift generic alpha and beta jobs to generic alpha and beta feature tags #34456
• Switch cluster trust bundle e2e tests to feature-gate tagging kubernetes#130567
• WIP: POC of beta promotion with e2es kubernetes#130572
• e2e framework: add [Feature:Alpha] or [Feature:Beta] via WithFeatureGate kubernetes#130580

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.