kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #8480 from deads2k/ga-disableable 

explain that GA features must be disableable if it is the first release they are default-on
This commit is contained in:
Kubernetes Prow Robot 2025-06-05 14:34:38 -07:00 committed by GitHub
parent e40e687af4 286a24a919
commit 097b1fefa6
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
contributors/devel/sig-architecture/feature-gates.md
View File

@ -175,8 +175,12 @@ Kubernetes. For example, the CSIMigration feature gates looked like this:
GA features are always on by default, and usually cannot be disabled.
Sometimes (rarely) a GA feature is allowed to be disabled (`LockToDefault:
false`). This indicates that while this feature is GA, they need to take some
Sometimes (rarely) a GA feature is allowed to be disabled (`LockToDefault: false`).
This is used for features that are being enabled by default for the first time.
Such features must be disable-able in the first release they are on by default.
The most common case is when an entirely new API is created and is not enabled by
default until the serialization is stable (GA).
This can also indicate that while this feature is GA, they need to take some
other action outside of Kubernetes to use it. This gives some grace period for
users to take action, but such feature gates will eventually set
`LockToDefault` to `true` and then be retired, like normal.