StatefulSetStatus attribute availableReplicas set to required by mistake?

[ca-scribner]

What happened?

Looking at the swagger specifications for StatefulSetStatus, it defines availableReplicas as a required attribute. But looking at the description of availableReplicas, it states ...This is a beta field and enabled/disabled by StatefulSetMinReadySeconds feature gate. Should this in fact be a required attribute?

I come about this from using lightkube, a python package that generates models from the swagger definitions and thus builds a StatefulSetStatus that requires an attribute that is not enabled.

What did you expect to happen?

That only truly required attributes be required in the swagger definition

How can we reproduce it (as minimally and precisely as possible)?

Reproduction is not applicable as this is an issue with a spec

Anything else we need to know?

No response

Kubernetes version

Appeared in 1.22 (I believe) and affects current versions. Does not affect 1.21

Cloud provider

n/a

OS version

No response

Install tools

No response

Container runtime (CRI) and version (if applicable)

No response

Related plugins (CNI, CSI, ...) and versions (if applicable)

No response

[k8s-ci-robot]

@ca-scribner: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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/test-infra repository.

[neolit123]

alpha:
#100842
#100842 (review)
has +optional that is planned for removal in beta.
(+optional results in fields as non-required in the OpenAPI)

beta:
https://github.com/kubernetes/kubernetes/pull/104045/files
removes the +optional

this might be a question whether feature gate controlled fields must remain +optional until the feature gate is removed (and how would validation work in that case).
old feature gates graduations to beta enabled a feature by default.

a topic related to #108279 ?
but it does not apply to feature gates.

/kind documentation
/sig apps

[neolit123]

cc @ravisantoshgudimetla
(since you are the KEP author)

[liggitt]

new fields added to existing types must always be marked as +optional, since clients are not required to specify them

[liggitt]

please open a PR adding back the +optional tag, regenerate openapi, and open picks back to 1.23 and 1.22