Skip to content

Commit a3f297b

Browse files
committed
Use new feature_gate_name option
1 parent a936505 commit a3f297b

File tree

9 files changed

+15
-15
lines changed

9 files changed

+15
-15
lines changed

content/en/docs/concepts/architecture/garbage-collection.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -139,7 +139,7 @@ until disk usage reaches the `LowThresholdPercent` value.
139139

140140
#### Garbage collection for unused container images {#image-maximum-age-gc}
141141

142-
{{< feature-state for_k8s_version="v1.29" state="alpha" >}}
142+
{{< feature-state feature_gate_name="ImageMaximumGCAge" >}}
143143

144144
As an alpha feature, you can specify the maximum time a local image can be unused for,
145145
regardless of disk usage. This is a kubelet setting that you configure for each node.

content/en/docs/concepts/architecture/leases.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ instances are on stand-by.
3333

3434
## API server identity
3535

36-
{{< feature-state for_k8s_version="v1.26" state="beta" >}}
36+
{{< feature-state feature_gate_name="APIServerIdentity" >}}
3737

3838
Starting in Kubernetes v1.26, each `kube-apiserver` uses the Lease API to publish its identity to the
3939
rest of the system. While not particularly useful on its own, this provides a mechanism for clients to

content/en/docs/concepts/architecture/mixed-version-proxy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ weight: 220
88

99
<!-- overview -->
1010

11-
{{< feature-state state="alpha" for_k8s_version="v1.28" >}}
11+
{{< feature-state feature_gate_name="UnknownVersionInteroperabilityProxy" >}}
1212

1313
Kubernetes {{< skew currentVersion >}} includes an alpha feature that lets an
1414
{{< glossary_tooltip text="API Server" term_id="kube-apiserver" >}}

content/en/docs/concepts/architecture/nodes.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -280,7 +280,7 @@ If you want to explicitly reserve resources for non-Pod processes, see
280280

281281
## Node topology
282282

283-
{{< feature-state state="stable" for_k8s_version="v1.27" >}}
283+
{{< feature-state feature_gate_name="TopologyManager" >}}
284284

285285
If you have enabled the `TopologyManager`
286286
[feature gate](/docs/reference/command-line-tools-reference/feature-gates/), then
@@ -290,7 +290,7 @@ for more information.
290290

291291
## Graceful node shutdown {#graceful-node-shutdown}
292292

293-
{{< feature-state state="beta" for_k8s_version="v1.21" >}}
293+
{{< feature-state feature_gate_name="GracefulNodeShutdown" >}}
294294

295295
The kubelet attempts to detect node system shutdown and terminates pods running on the node.
296296

@@ -374,7 +374,7 @@ Message: Pod was terminated in response to imminent node shutdown.
374374

375375
### Pod Priority based graceful node shutdown {#pod-priority-graceful-node-shutdown}
376376

377-
{{< feature-state state="beta" for_k8s_version="v1.24" >}}
377+
{{< feature-state feature_gate_name="GracefulNodeShutdownBasedOnPodPriority" >}}
378378

379379
To provide more flexibility during graceful node shutdown around the ordering
380380
of pods during shutdown, graceful node shutdown honors the PriorityClass for
@@ -471,7 +471,7 @@ are emitted under the kubelet subsystem to monitor node shutdowns.
471471

472472
## Non-graceful node shutdown handling {#non-graceful-node-shutdown}
473473

474-
{{< feature-state state="stable" for_k8s_version="v1.28" >}}
474+
{{< feature-state feature_gate_name="NodeOutOfServiceVolumeDetach" >}}
475475

476476
A node shutdown action may not be detected by kubelet's Node Shutdown Manager,
477477
either because the command does not trigger the inhibitor locks mechanism used by
@@ -515,7 +515,7 @@ During a non-graceful shutdown, Pods are terminated in the two phases:
515515

516516
## Swap memory management {#swap-memory}
517517

518-
{{< feature-state state="beta" for_k8s_version="v1.28" >}}
518+
{{< feature-state feature_gate_name="NodeSwap" >}}
519519

520520
To enable swap on a node, the `NodeSwap` feature gate must be enabled on
521521
the kubelet, and the `--fail-swap-on` command line flag or `failSwapOn`

content/en/docs/concepts/cluster-administration/system-logs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -238,7 +238,7 @@ The `logrotate` tool rotates logs daily, or once the log size is greater than 10
238238

239239
## Log query
240240

241-
{{< feature-state for_k8s_version="v1.27" state="alpha" >}}
241+
{{< feature-state feature_gate_name="NodeLogQuery" >}}
242242

243243
To help with debugging issues on nodes, Kubernetes v1.27 introduced a feature that allows viewing logs of services
244244
running on the node. To use the feature, ensure that the `NodeLogQuery`

content/en/docs/concepts/cluster-administration/system-traces.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ For more information about the `TracingConfiguration` struct, see
7676

7777
### kubelet traces
7878

79-
{{< feature-state for_k8s_version="v1.27" state="beta" >}}
79+
{{< feature-state feature_gate_name="KubeletTracing" >}}
8080

8181
The kubelet CRI interface and authenticated http servers are instrumented to generate
8282
trace spans. As with the apiserver, the endpoint and sampling rate are configurable.

content/en/docs/concepts/containers/images.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -161,7 +161,7 @@ which is 300 seconds (5 minutes).
161161

162162
### Image pull per runtime class
163163

164-
{{< feature-state for_k8s_version="v1.29" state="alpha" >}}
164+
{{< feature-state feature_gate_name="RuntimeClassInImageCriApi" >}}
165165
Kubernetes includes alpha support for performing image pulls based on the RuntimeClass of a Pod.
166166

167167
If you enable the `RuntimeClassInImageCriApi` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/),

content/en/docs/concepts/scheduling-eviction/assign-pod-node.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -360,7 +360,7 @@ null `namespaceSelector` matches the namespace of the Pod where the rule is defi
360360

361361
#### matchLabelKeys
362362

363-
{{< feature-state for_k8s_version="v1.29" state="alpha" >}}
363+
{{< feature-state feature_gate_name="MatchLabelKeysInPodAffinity" >}}
364364

365365
{{< note >}}
366366
<!-- UPDATE THIS WHEN PROMOTING TO BETA -->
@@ -410,7 +410,7 @@ spec:
410410

411411
#### mismatchLabelKeys
412412

413-
{{< feature-state for_k8s_version="v1.29" state="alpha" >}}
413+
{{< feature-state feature_gate_name="MatchLabelKeysInPodAffinity" >}}
414414

415415
{{< note >}}
416416
<!-- UPDATE THIS WHEN PROMOTING TO BETA -->

content/en/docs/concepts/services-networking/service.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -621,7 +621,7 @@ can define your own (provider specific) annotations on the Service that specify
621621

622622
#### Load balancers with mixed protocol types
623623

624-
{{< feature-state for_k8s_version="v1.26" state="stable" >}}
624+
{{< feature-state feature_gate_name="MixedProtocolLBService" >}}
625625

626626
By default, for LoadBalancer type of Services, when there is more than one port defined, all
627627
ports must have the same protocol, and the protocol must be one which is supported
@@ -670,7 +670,7 @@ Unprefixed names are reserved for end-users.
670670

671671
#### Specifying IPMode of load balancer status {#load-balancer-ip-mode}
672672

673-
{{< feature-state for_k8s_version="v1.29" state="alpha" >}}
673+
{{< feature-state feature_gate_name="LoadBalancerIPMode" >}}
674674

675675
Starting as Alpha in Kubernetes 1.29,
676676
a [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)

0 commit comments

Comments
 (0)