From 0686d4b7d64727bdd987135c33a8679314036e3b Mon Sep 17 00:00:00 2001 From: "zhenghao.zhu" Date: Mon, 15 May 2023 18:18:45 +0800 Subject: [PATCH] remove duplication of NewVolumeManagerReconstruction --- .../command-line-tools-reference/feature-gates.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md index e7c812dce6c..5aa61750270 100644 --- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md +++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md @@ -617,8 +617,10 @@ Each feature gate is designed for enabling/disabling a specific feature: - `MultiCIDRRangeAllocator`: Enables the MultiCIDR range allocator. - `MultiCIDRServiceAllocator`: Track IP address allocations for Service cluster IPs using IPAddress objects. - `NetworkPolicyStatus`: Enable the `status` subresource for NetworkPolicy objects. -- `NewVolumeManagerReconstruction`: Enable improved discovery of mounted volumes during kubelet - startup. +- `NewVolumeManagerReconstruction`: Enables improved discovery of mounted volumes during kubelet + startup. Since this code has been significantly refactored, we allow to opt-out in case kubelet + gets stuck at the startup or is not unmounting volumes from terminated Pods. Note that this + refactoring was behind `SELinuxMountReadWriteOncePod` alpha feature gate in Kubernetes 1.25. Before Kubernetes v1.25, the kubelet used different default behavior for discovering mounted volumes during the kubelet startup. If you disable this feature gate (it's enabled by default), you select @@ -626,10 +628,6 @@ Each feature gate is designed for enabling/disabling a specific feature: In Kubernetes v1.25 and v1.26, this behavior toggle was part of the `SELinuxMountReadWriteOncePod` feature gate. -- `NewVolumeManagerReconstruction`: Enables improved discovery of mounted volumes during kubelet - startup. Since this code has been significantly refactored, we allow to opt-out in case kubelet - gets stuck at the startup or is not unmounting volumes from terminated Pods. Note that this - refactoring was behind `SELinuxMountReadWriteOncePod` alpha feature gate in Kubernetes 1.25. - `NodeInclusionPolicyInPodTopologySpread`: Enable using `nodeAffinityPolicy` and `nodeTaintsPolicy` in [Pod topology spread constraints](/docs/concepts/scheduling-eviction/topology-spread-constraints/) when calculating pod topology spread skew.