prevent enabling beta by default for new api groups

[deads2k]

In support of kubernetes/enhancements#3137 .

This identifies and hardcodes the list of legacy beta resources that were enabled prior to 1.22. No new beta APIs should be enabled by default.

kubernetes/test-infra#25148 attempts to create a new job definition to test new beta APIs.

/kind feature
/sig api-machinery
/priority important-soon

NONE

[deads2k]

/hold

I need to think through precedence of preferences.

1. a user specifying a resource enable/disable
2. a user specifying a version enable/disable
3. a user specifying an api stability enable/disable
4. a hardcoded resource enable/disable
5. a hardcoded version enable/disable

I think that's what I want. But will it cause hairloss.

[leilajal]

/triage accepted

[deads2k]

we agreed on behavior

/hold cancel

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k

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:

• cmd/kube-apiserver/OWNERS [deads2k]
• pkg/controlplane/OWNERS [deads2k]
• pkg/registry/OWNERS [deads2k]
• staging/src/k8s.io/apiserver/OWNERS [deads2k]
• test/integration/apiserver/OWNERS [deads2k]

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

[deads2k]

{"level":"warn","ts":"2022-02-23T19:24:36.305Z","logger":"etcd-client","caller":"v3/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc0333bb180/#initially=[http://127.0.0.1:2379]","attempt":0,"error":"rpc error: code = Unavailable desc = keepalive ping failed to receive ACK within timeout"}

hmm.....

/retest
/hold to check integration results.

[deads2k]

/hold cancel

[liggitt]

not a problem, but curious why only this one has an expiry and none of the other beta versions do

[liggitt]

/lgtm