Getting CRD Validation to Beta

[colemickens]

This is a tracking issue for discussion about what needs to be done in order to move CRD Validation to Beta for 1.9.

Related links:

• CRD Umbrella Issue (feature repo)
• CRD Validation feature request
• CRD Validation Proposal (community repo)
• CRD Validation implementation PR (alpha)

Additional discussions:

• CRD Validation using OpenAPI v3

[colemickens]

/sig api-machinery

[sttts]

Seeing these features, but they are not necessarily blocking for beta:

• defaulting apiextensions: add defaulting for customresource validation #52034
• readonly fields
• JSON schema references to other APIGroups, e.g. embedding a PodSpec schema.

As far as I see, all of these can be added post-beta. Right now we forbid setting default values and marking fields as readonly. So nobody using validation now (or with a beta without these features) will be surprised when we add them.

JSON schema references to other APIGroups just do not exist right now. We have to "invent" a reference name space and resolve the references. This can be added anytime as an additional feature.

[sttts]

As discussed today in the sig-api-machinery meeting there are no objections to move forward to beta. @colemickens will add updates for that in the features repo.

[nikhita]

/area third-party-resource
/cc @deads2k @enisoc @mbohlool @munnerz

[nikhita]

Ref #54579.

[deads2k]

As discussed today in the sig-api-machinery meeting there are no objections to move forward to beta. @colemickens will add updates for that in the features repo.

Agree.

[colemickens]

It looks like @sttts has already updated the only tracking issue we have in kubernetes/features. I've sent the PR for the feature gate promotion: #54647