Fix feature-state typo

This commit is contained in:
Jordan Liggitt
2020-04-09 13:28:16 -04:00
parent 476f7b4765
commit e67c5710a6
2 changed files with 8 additions and 8 deletions
@@ -28,7 +28,7 @@ level of your CustomResourceDefinitions or advance your API to a new version wit
## Overview ## Overview
{{< feature-state state="stable" for_kubernetes_version="1.16" >}} {{< feature-state state="stable" for_k8s_version="1.16" >}}
The CustomResourceDefinition API provides a workflow for introducing and upgrading The CustomResourceDefinition API provides a workflow for introducing and upgrading
to new versions of a CustomResourceDefinition. to new versions of a CustomResourceDefinition.
@@ -276,7 +276,7 @@ the version.
## Webhook conversion ## Webhook conversion
{{< feature-state state="stable" for_kubernetes_version="1.16" >}} {{< feature-state state="stable" for_k8s_version="1.16" >}}
{{< note >}} {{< note >}}
Webhook conversion is available as beta since 1.15, and as alpha since Kubernetes 1.13. The Webhook conversion is available as beta since 1.15, and as alpha since Kubernetes 1.13. The
@@ -243,7 +243,7 @@ If you later recreate the same CustomResourceDefinition, it will start out empty
## Specifying a structural schema ## Specifying a structural schema
{{< feature-state state="stable" for_kubernetes_version="1.16" >}} {{< feature-state state="stable" for_k8s_version="1.16" >}}
CustomResources traditionally store arbitrary JSON (next to `apiVersion`, `kind` and `metadata`, which is validated by the API server implicitly). With [OpenAPI v3.0 validation](/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/#validation) a schema can be specified, which is validated during creation and updates, compare below for details and limits of such a schema. CustomResources traditionally store arbitrary JSON (next to `apiVersion`, `kind` and `metadata`, which is validated by the API server implicitly). With [OpenAPI v3.0 validation](/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/#validation) a schema can be specified, which is validated during creation and updates, compare below for details and limits of such a schema.
@@ -364,7 +364,7 @@ Structural schemas are a requirement for `apiextensions.k8s.io/v1`, and disables
### Pruning versus preserving unknown fields ### Pruning versus preserving unknown fields
{{< feature-state state="stable" for_kubernetes_version="1.16" >}} {{< feature-state state="stable" for_k8s_version="1.16" >}}
CustomResourceDefinitions traditionally store any (possibly validated) JSON as is in etcd. This means that unspecified fields (if there is a [OpenAPI v3.0 validation schema](/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/#validation) at all) are persisted. This is in contrast to native Kubernetes resources like e.g. a pod where unknown fields are dropped before being persisted to etcd. We call this "pruning" of unknown fields. CustomResourceDefinitions traditionally store any (possibly validated) JSON as is in etcd. This means that unspecified fields (if there is a [OpenAPI v3.0 validation schema](/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/#validation) at all) are persisted. This is in contrast to native Kubernetes resources like e.g. a pod where unknown fields are dropped before being persisted to etcd. We call this "pruning" of unknown fields.
@@ -604,7 +604,7 @@ meaning all finalizers have been executed.
### Validation ### Validation
{{< feature-state state="stable" for_kubernetes_version="1.16" >}} {{< feature-state state="stable" for_k8s_version="1.16" >}}
Validation of custom objects is possible via Validation of custom objects is possible via
[OpenAPI v3 schemas](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#schemaObject) or [validatingadmissionwebhook](/docs/reference/access-authn-authz/admission-controllers/#validatingadmissionwebhook). In `apiextensions.k8s.io/v1` schemas are required, in `apiextensions.k8s.io/v1beta1` they are optional. [OpenAPI v3 schemas](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#schemaObject) or [validatingadmissionwebhook](/docs/reference/access-authn-authz/admission-controllers/#validatingadmissionwebhook). In `apiextensions.k8s.io/v1` schemas are required, in `apiextensions.k8s.io/v1beta1` they are optional.
@@ -781,7 +781,7 @@ crontab "my-new-cron-object" created
### Defaulting ### Defaulting
{{< feature-state state="beta" for_kubernetes_version="1.16" >}} {{< feature-state state="beta" for_k8s_version="1.16" >}}
{{< note >}} {{< note >}}
Defaulting is available as beta since 1.16 in `apiextensions.k8s.io/v1` CustomResourceDefinitions, and hence enabled by default for most clusters (feature gate `CustomResourceDefaulting`, refer to the [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) documentation). Defaulting is available as beta since 1.16 in `apiextensions.k8s.io/v1` CustomResourceDefinitions, and hence enabled by default for most clusters (feature gate `CustomResourceDefaulting`, refer to the [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) documentation).
@@ -866,7 +866,7 @@ Default values for `metadata` fields of `x-kubernetes-embedded-resources: true`
### Publish Validation Schema in OpenAPI v2 ### Publish Validation Schema in OpenAPI v2
{{< feature-state state="stable" for_kubernetes_version="1.16" >}} {{< feature-state state="stable" for_k8s_version="1.16" >}}
{{< note >}} {{< note >}}
OpenAPI v2 Publishing is available as beta since 1.15, and as alpha since 1.14. The OpenAPI v2 Publishing is available as beta since 1.15, and as alpha since 1.14. The
@@ -1051,7 +1051,7 @@ The column's `format` controls the style used when `kubectl` prints the value.
### Subresources ### Subresources
{{< feature-state state="stable" for_kubernetes_version="1.16" >}} {{< feature-state state="stable" for_k8s_version="1.16" >}}
Custom resources support `/status` and `/scale` subresources. Custom resources support `/status` and `/scale` subresources.