From e4731338d3a5b503f30fbdd968aa363e413c469d Mon Sep 17 00:00:00 2001 From: Tim Bannister Date: Fri, 16 Feb 2024 10:46:59 +0000 Subject: [PATCH] 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 --- content/en/docs/concepts/overview/kubernetes-api.md | 4 ++-- content/en/docs/concepts/workloads/pods/pod-qos.md | 2 +- .../reference/access-authn-authz/service-accounts-admin.md | 6 +++--- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/content/en/docs/concepts/overview/kubernetes-api.md b/content/en/docs/concepts/overview/kubernetes-api.md index ceec7e1eac..f7e6da3d86 100644 --- a/content/en/docs/concepts/overview/kubernetes-api.md +++ b/content/en/docs/concepts/overview/kubernetes-api.md @@ -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 diff --git a/content/en/docs/concepts/workloads/pods/pod-qos.md b/content/en/docs/concepts/workloads/pods/pod-qos.md index 491a4af2ef..e656208958 100644 --- a/content/en/docs/concepts/workloads/pods/pod-qos.md +++ b/content/en/docs/concepts/workloads/pods/pod-qos.md @@ -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` diff --git a/content/en/docs/reference/access-authn-authz/service-accounts-admin.md b/content/en/docs/reference/access-authn-authz/service-accounts-admin.md index 1f1fa64f60..92e631fc20 100644 --- a/content/en/docs/reference/access-authn-authz/service-accounts-admin.md +++ b/content/en/docs/reference/access-authn-authz/service-accounts-admin.md @@ -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