Drop dead beta storage and validation code

[liggitt]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Drops the storage and validation code that was only exercised by the beta versions no longer served since 1.22.

Does this PR introduce a user-facing change?

kube-apiserver: The `rbac.authorization.k8s.io/v1alpha1` API version is removed; use the `rbac.authorization.k8s.io/v1` API, available since v1.8. The `scheduling.k8s.io/v1alpha1` API version is removed; use the `scheduling.k8s.io/v1` API, available since v1.14.

/assign @deads2k

[liggitt]

/priority important-soon
/triage accepted

[liggitt]

/hold for reviews

[liggitt]

/milestone v1.23

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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:

• api/OWNERS [liggitt]
• cmd/kube-apiserver/OWNERS [liggitt]
• pkg/apis/OWNERS [liggitt]
• pkg/controlplane/OWNERS [liggitt]
• pkg/registry/OWNERS [liggitt]
• staging/src/k8s.io/apiextensions-apiserver/OWNERS [liggitt]
• staging/src/k8s.io/apiextensions-apiserver/pkg/apis/OWNERS [liggitt]
• staging/src/k8s.io/kube-aggregator/OWNERS [liggitt]
• test/integration/etcd/OWNERS [liggitt]

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

[deads2k]

Now that's a cathartic PR.

/lgtm

[liggitt]

/assign @robscott
PTAL at the Drop legacy validation logic for networking API commit

/assign @msau42
PTAL at the Drop legacy status logic for volumeattachments API commit

[robscott]

This is great, thanks @liggitt! Networking commit LGTM.

[msau42]

/lgtm
for volumeattachment validation

[liggitt]

/hold cancel

[k8s-triage-robot]

This PR may require API review.

If so, when the changes are ready, complete the pre-review checklist and request an API review.

Status of requested reviews is tracked in the API Review project.

[tengqm]

Why https://github.com/kubernetes/kubernetes/tree/master/pkg/apis/rbac/v1alpha1 is still there and https://github.com/kubernetes/kubernetes/tree/master/pkg/apis/scheduling/v1alpha1 is still there if both APIs are dropped?

[liggitt]

All code related to serving those versions was removed, but the types and conversions still exist to support reading/converting data stored in etcd in those versions

[tengqm]

So ... those schemes are still installed, just for conversions convenience?

[liggitt]

they're installed so that pre-release data exists in etcd, it can still be read/converted in order to be served as v1 objects in response to a v1 API request

[tengqm]

@liggitt Thanks for the clarification.