Mark NewVolumeManagerReconstruction as GA
parent
fe2efe0465
commit
ae56379254
|
@ -13,16 +13,13 @@ stages:
|
|||
- stage: beta
|
||||
defaultValue: true
|
||||
fromVersion: "1.28"
|
||||
toVersion: "1.29"
|
||||
- stage: stable
|
||||
defaultValue: true
|
||||
fromVersion: "1.30"
|
||||
---
|
||||
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.
|
||||
|
||||
<!-- remove next 2 paragraphs when feature graduates to GA -->
|
||||
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
|
||||
the legacy discovery behavior.
|
||||
|
||||
In Kubernetes v1.25 and v1.26, this behavior toggle was part of the `SELinuxMountReadWriteOncePod`
|
||||
feature gate.
|
||||
startup. Since this code has been significantly refactored, Kubernetes versions 1.25 - 1.29
|
||||
allowed 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 versions 1.25 - 1.26.
|
||||
|
|
Loading…
Reference in New Issue