Merge pull request #49367 from windsonsea/new5

[zh] Rename feature-gates E-K and add new gates
pull/49496/head
Kubernetes Prow Robot 2025-01-19 01:32:34 -08:00 committed by GitHub
commit 18206ce8fc
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
80 changed files with 149 additions and 7 deletions

View File

@ -0,0 +1,22 @@
---
title: APIServingWithRoute
content_type: feature_gate
_build:
list: never
render: false
stages:
- stage: alpha
defaultValue: false
fromVersion: "1.30"
---
<!--
This feature gate enables an API server performance improvement:
the API server can use separate goroutines (lightweight threads managed by the Go runtime)
to serve [**watch**](/docs/reference/using-api/api-concepts/#efficient-detection-of-changes)
requests.
-->
这个特性门控可以启用一项 API 服务器性能提升API 服务器可以使用独立的 Goroutine
(由 Go 运行时管理的轻量级线程)来处理
[**watch**](/zh-cn/docs/reference/using-api/api-concepts/#efficient-detection-of-changes) 请求。

View File

@ -8,7 +8,10 @@ _build:
stages:
- stage: deprecated
defaultValue: false
fromVersion: "1.28"
fromVersion: "1.28"
toVersion: "1.30"
removed: true
---
<!--
This feature gate controls the point at which a default value for

View File

@ -18,6 +18,7 @@ stages:
defaultValue: true
fromVersion: "1.24"
---
<!--
Allows for storage-originated bookmark (progress
notify) events to be delivered to the users. This is only applied to watch operations.

View File

@ -14,6 +14,7 @@ stages:
defaultValue: true
fromVersion: "1.31"
---
<!--
Enables Indexed Jobs to be scaled up or down by mutating both
`spec.completions` and `spec.parallelism` together such that `spec.completions == spec.parallelism`.

View File

@ -27,6 +27,7 @@ stages:
removed: true
---
<!--
Enables EndpointSlices for more scalable and extensible
network endpoints. See [Enabling EndpointSlices](/docs/concepts/services-networking/endpoint-slices/).

View File

@ -23,6 +23,7 @@ stages:
removed: true
---
<!--
When enabled, kube-proxy running
on Linux will use EndpointSlices as the primary data source instead of

View File

@ -23,6 +23,7 @@ stages:
removed: true
---
<!--
Enable the ability to add
{{< glossary_tooltip text="ephemeral containers" term_id="ephemeral-container" >}}

View File

@ -23,6 +23,7 @@ stages:
removed: true
---
<!--
Enable pods to be scheduled evenly across topology domains. See
[Pod Topology Spread Constraints](/docs/concepts/scheduling-eviction/topology-spread-constraints/).

View File

@ -8,8 +8,9 @@ _build:
stages:
- stage: alpha
defaultValue: false
fromVersion: "1.25"
fromVersion: "1.26"
---
<!--
Enable support for the kubelet to receive container life cycle events from the
{{< glossary_tooltip text="container runtime" term_id="container-runtime" >}} via

View File

@ -10,6 +10,7 @@ stages:
defaultValue: true
fromVersion: "1.20"
---
<!--
Ensure kubelet respects exec probe timeouts.
This feature gate exists in case any of your existing workloads depend on a

View File

@ -23,6 +23,7 @@ stages:
removed: true
---
<!--
Enable expanding in-use PVCs. See
[Resizing an in-use PersistentVolumeClaim](/docs/concepts/storage/persistent-volumes/#resizing-an-in-use-persistentvolumeclaim).

View File

@ -23,6 +23,7 @@ stages:
removed: true
---
<!--
Enable the expanding of persistent volumes. See
[Expanding Persistent Volumes Claims](/docs/concepts/storage/persistent-volumes/#expanding-persistent-volumes-claims).

View File

@ -20,6 +20,7 @@ stages:
toVersion: "1.29"
removed: true
---
<!--
Enable kubelet and kube-apiserver to allow more DNS
search paths and longer list of DNS search paths. This feature requires container

View File

@ -19,6 +19,7 @@ stages:
removed: true
---
<!--
Enable annotating specific pods as *critical*
so that their [scheduling is guaranteed](/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/).

View File

@ -16,6 +16,7 @@ stages:
toVersion: "1.29"
removed: true
---
<!--
Enabling the defaulting user
namespace to host. This is for containers that are using other host namespaces,

View File

@ -21,6 +21,7 @@ stages:
removed: true
---
<!--
Enables the gRPC probe method for {Liveness,Readiness,Startup}Probe.
See [Configure Liveness, Readiness and Startup Probes](/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-a-grpc-liveness-probe).

View File

@ -23,6 +23,7 @@ stages:
removed: true
---
<!--
Enables ephemeral, inline volumes that support all features
of normal volumes (can be provided by third-party storage vendors, storage capacity tracking,

View File

@ -14,6 +14,7 @@ stages:
defaultValue: true
fromVersion: "1.21"
---
<!--
Enables support for graceful shutdown in kubelet.
During a system shutdown, kubelet will attempt to detect the shutdown event

View File

@ -14,6 +14,7 @@ stages:
defaultValue: true
fromVersion: "1.24"
---
<!--
Enables the kubelet to check Pod priorities
when shutting down a node gracefully.

View File

@ -0,0 +1,19 @@
---
title: InPlacePodVerticalScalingAllocatedStatus
content_type: feature_gate
_build:
list: never
render: false
stages:
- stage: alpha
defaultValue: false
fromVersion: "1.32"
---
<!--
Enables the `allocatedResources` field in the container status.
This feature requires the `InPlacePodVerticalScaling` gate be enabled as well.
-->
启用容器状态中的 `allocatedResources` 字段。
此特性还需要启用 `InPlacePodVerticalScaling` 门控。

View File

@ -0,0 +1,21 @@
---
title: InPlacePodVerticalScalingExclusiveCPUs
content_type: feature_gate
_build:
list: never
render: false
stages:
- stage: alpha
defaultValue: false
fromVersion: "1.32"
---
<!--
Enable resource resizing for containers in Guaranteed pods with integer CPU requests.
It applies only in nodes with `InPlacePodVerticalScaling` and `CPUManager` features enabled,
and the CPUManager policy set to `static`.
-->
在 CPU 请求数为整数的 Guaranteed Pod 中启用容器的资源调整特性。
此特性门控仅适用于启用 `InPlacePodVerticalScaling``CPUManager`
特性且 CPUManager 策略设置为 `static` 的节点。

View File

@ -10,6 +10,10 @@ stages:
- stage: alpha
defaultValue: false
fromVersion: "1.30"
toVersion: "1.31"
- stage: beta
defaultValue: true
fromVersion: "1.32"
---
<!--

View File

@ -12,7 +12,10 @@ stages:
toVersion: "1.28"
- stage: stable
defaultValue: true
fromVersion: "1.29"
fromVersion: "1.29"
toVersion: "1.31"
removed: true
---
<!--

View File

@ -0,0 +1,21 @@
---
title: RemoteRequestHeaderUID
content_type: feature_gate
_build:
list: never
render: false
stages:
- stage: alpha
defaultValue: false
fromVersion: "1.32"
---
<!--
Enable the API server to accept UIDs (user IDs) via request header authentication.
This will also make the `kube-apiserver`'s API aggregator add UIDs via standard headers when
forwarding requests to the servers serving the aggregated API.
-->
允许 API 服务器通过请求头身份认证来接受 UID用户 ID
`kube-apiserver` 的 API 聚合器将请求转发到提供聚合 API 的服务器时,
`kube-apiserver` 的 API 聚合器也将通过标准请求头添加 UID。

View File

@ -0,0 +1,19 @@
---
title: SeparateCacheWatchRPC
content_type: feature_gate
_build:
list: never
render: false
stages:
- stage: beta
defaultValue: true
fromVersion: "1.20"
---
<!--
Allows the API server watch cache to create a watch on a dedicated RPC.
This prevents watch cache from being starved by other watches.
-->
允许 API 服务器的监视缓存在专用的 RPC 上创建 watch。
这防止了监视缓存被其他 watch 所占用。

View File

@ -19,7 +19,7 @@ stages:
- stage: stable
defaultValue: true
fromVersion: "1.18"
toVersion: "1.20"
toVersion: "1.18"
removed: true
---

View File

@ -17,7 +17,9 @@ stages:
---
<!--
Enables KMS v1 API for encryption at rest. See [Using a KMS Provider for data encryption](/docs/tasks/administer-cluster/kms-provider) for more details.
Enables KMS v1 API for encryption at rest. See
[Using a KMS Provider for data encryption](/docs/tasks/administer-cluster/kms-provider)
for more details.
-->
启用 KMS v1 API 以实现静态加密。
详情参见[使用 KMS 驱动进行数据加密](/zh-cn/docs/tasks/administer-cluster/kms-provider/)。

View File

@ -16,11 +16,16 @@ stages:
toVersion: "1.28"
- stage: stable
defaultValue: true
fromVersion: "1.29"
fromVersion: "1.29"
toVersion: "1.31"
removed: true
---
<!--
Enables KMS v2 API for encryption at rest. See [Using a KMS Provider for data encryption](/docs/tasks/administer-cluster/kms-provider) for more details.
Enables KMS v2 API for encryption at rest. See
[Using a KMS Provider for data encryption](/docs/tasks/administer-cluster/kms-provider)
for more details.
-->
启用 KMS v2 API 以实现静态加密。
详情参见[使用 KMS 驱动进行数据加密](/zh-cn/docs/tasks/administer-cluster/kms-provider/)。