Switch some feature-state shortcodes to be data driven
When the feature gates graduate (or get deprecated), the associated shortcode will update automatically. Co-authored-by: Dipesh Rawat <rawat.dipesh@gmail.com>
This commit is contained in:
parent
ad537b9d83
commit
e4731338d3
|
|
@ -82,7 +82,7 @@ packages that define the API objects.
|
|||
|
||||
### OpenAPI V3
|
||||
|
||||
{{< feature-state state="stable" for_k8s_version="v1.27" >}}
|
||||
{{< feature-state feature_gate_name="OpenAPIV3" >}}
|
||||
|
||||
Kubernetes supports publishing a description of its APIs as OpenAPI v3.
|
||||
|
||||
|
|
@ -167,7 +167,7 @@ cluster.
|
|||
|
||||
### Aggregated Discovery
|
||||
|
||||
{{< feature-state state="beta" for_k8s_version="v1.27" >}}
|
||||
{{< feature-state feature_gate_name="AggregatedDiscoveryEndpoint" >}}
|
||||
|
||||
Kubernetes offers beta support for aggregated discovery, publishing
|
||||
all resources supported by a cluster through two endpoints (`/api` and
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@ Containers in a Pod can request other resources (not CPU or memory) and still be
|
|||
|
||||
## Memory QoS with cgroup v2
|
||||
|
||||
{{< feature-state for_k8s_version="v1.22" state="alpha" >}}
|
||||
{{< feature-state feature-gate-name="MemoryQoS" >}}
|
||||
|
||||
Memory QoS uses the memory controller of cgroup v2 to guarantee memory resources in Kubernetes.
|
||||
Memory requests and limits of containers in pod are used to set specific interfaces `memory.min`
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ for a number of reasons:
|
|||
|
||||
## Bound service account token volume mechanism {#bound-service-account-token-volume}
|
||||
|
||||
{{< feature-state for_k8s_version="v1.22" state="stable" >}}
|
||||
{{< feature-state feature_gate_name="BoundServiceAccountTokenVolume" >}}
|
||||
|
||||
By default, the Kubernetes control plane (specifically, the
|
||||
[ServiceAccount admission controller](#serviceaccount-admission-controller))
|
||||
|
|
@ -249,7 +249,7 @@ it does the following when a Pod is created:
|
|||
|
||||
### Legacy ServiceAccount token tracking controller
|
||||
|
||||
{{< feature-state for_k8s_version="v1.28" state="stable" >}}
|
||||
{{< feature-state feature_gate_name="LegacyServiceAccountTokenTracking" >}}
|
||||
|
||||
This controller generates a ConfigMap called
|
||||
`kube-system/kube-apiserver-legacy-service-account-token-tracking` in the
|
||||
|
|
@ -258,7 +258,7 @@ account tokens began to be monitored by the system.
|
|||
|
||||
### Legacy ServiceAccount token cleaner
|
||||
|
||||
{{< feature-state for_k8s_version="v1.29" state="beta" >}}
|
||||
{{< feature-state feature_gate_name="LegacyServiceAccountTokenCleanUp" >}}
|
||||
|
||||
The legacy ServiceAccount token cleaner runs as part of the
|
||||
`kube-controller-manager` and checks every 24 hours to see if any auto-generated
|
||||
|
|
|
|||
Loading…
Reference in New Issue