KEP-4222: Update beta requirements and target for 1.37.

[benluddy]

• One-line PR description: Adding found beta requirements and updating beta target to 1.37.

• Issue link: CBOR Serializer #4222

• Other comments: Consolidates KEP-4222: Add streaming list encode requirement to CBOR KEP. #5459 and KEP-4222: Add requirement to support discovery, statusz, etc. #5740.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: benluddy
Once this PR has been reviewed and has the lgtm label, please assign sttts for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• keps/sig-api-machinery/OWNERS

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

[jpbetz]

+1 this is essential

[jpbetz]

I just hit a CBOR issue today I wanted to mention.

For the field GroupPriorityMinimum in staging/src/k8s.io/kube-aggregator/pkg/apis/apiregistration/v1/types.go I had added an entry to test/integration/etcd/data.gosomething like: "spec": {"group": "foo.com", "version": "as2", "groupPriorityMinimum":100, "versionPriority":10}`. This works fine for JSON but breaks for CBOR due to a float vs int issue.

[jpbetz]

This might be a problem in common ecosystem workflows? I'm imagining something like dynClient.Resource(...).Create(...) with a yaml.Unmarshal or json.Unmarshal of a type like APIService with int fields is going to end up with floats sent by the client and an error when CBOR is enabled