Skip to content

Commit

Permalink
Switch some feature-state shortcodes to be data driven
Browse files Browse the repository at this point in the history
When the feature gates graduate (or get deprecated), the associated
shortcode will update automatically.

Co-authored-by: Dipesh Rawat <rawat.dipesh@gmail.com>
  • Loading branch information
sftim and dipesh-rawat committed Feb 16, 2024
1 parent ad537b9 commit e473133
Show file tree
Hide file tree
Showing 3 changed files with 6 additions and 6 deletions.
4 changes: 2 additions & 2 deletions content/en/docs/concepts/overview/kubernetes-api.md
Expand Up @@ -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.

Expand Down Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion content/en/docs/concepts/workloads/pods/pod-qos.md
Expand Up @@ -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`
Expand Down
Expand Up @@ -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))
Expand Down Expand Up @@ -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
Expand All @@ -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
Expand Down

0 comments on commit e473133

Please sign in to comment.