Current documentation simply suggest
"Remove v1beta1 from the CustomResourceDefinition
status.storedVersions field."
but this cannot be done just with kubectl and
it's not so intuitive.
Adding an example to make it more clear.
Signed-off-by: Simone Tiraboschi <stirabos@redhat.com>
The Categories field for CRDs was documented as beta in 1.10 in #7439
mainly because CRDs were in beta back then.
The `feature-state` tag for this section was added in #2754, however
this section doesn't need a `feature-state` tag because the field is not
gated by any feature gate:
90851a0fb5/staging/src/k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1/types.go (L247-L251)
It is now safe to remove the feature-state tag. Moreover, CRDs are now
GA so the beta state is not accurate.
- It's now more precise regarding the format of finalizers (which have to
consist of a namespace and a name, separated by a forward slash or they
will get rejected by the apiserver, with the exception of built in ones)
- It's less repetitve in general
This change corrects the capitalization for the code blocks referring to
`statusReplicasPath` and `labelSelectorPath` to make the descriptive
text consistent with the code values.
The example on line 746-754, should has an image tag; with the image tag, the validation will fail with the error "validating data: ValidationError(CronTab.spec): unknown field "image"". Solution : Adding the image field on the CustomResourceDefinitions.
Tim Bannister
cici37
Jesse Butler
Kubernetes Prow Robot
Joe Betz
Dima Brusilovsky
Simone Tiraboschi
chenxuc
Qiming Teng
David Garvey
dancnfoo
Karen Bradshaw
Nikhita Raghunath
Antoine Pelisse
Jefftree
Jakob
Michael McCune
Qiming Teng
Savitha Raghunathan
Anna Jung
Richard Mokua
jimoosciuc
Jordan Liggitt