From 0d97e560fdd942feebedc09e48dc572961ba9264 Mon Sep 17 00:00:00 2001 From: Davanum Srinivas Date: Sat, 13 Mar 2021 11:10:09 -0500 Subject: Update contributors/devel/sig-architecture/feature-gates.md Co-authored-by: Elana Hashman --- contributors/devel/sig-architecture/feature-gates.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'contributors') diff --git a/contributors/devel/sig-architecture/feature-gates.md b/contributors/devel/sig-architecture/feature-gates.md index e1abe3ec..960b1264 100644 --- a/contributors/devel/sig-architecture/feature-gates.md +++ b/contributors/devel/sig-architecture/feature-gates.md @@ -30,7 +30,7 @@ This enables folks to switch on the feature using the command line. By default i ## Beta Features * `PreRelease` is set to `featuregate.Beta` -* `Default` is always set to `true` +* `Default` is set to `true` * `LockToDefault` is not set. Defaults to `false` This enables the feature to be on and available in the default installation of kubernetes. @@ -60,4 +60,3 @@ Also note that when we set `LockToDefault` to `true`, we remove all references ( ## Other scenarios Sometimes we use`{Default: true, PreRelease: featuregate.Beta}` for keeping legacy behavior (see `LegacyNodeRoleBehavior`) on and when we basically want to drop the legacy behavior with new default behavior. So at GA we will end up with `{Default: false, PreRelease: featuregate.GA, LockToDefault: true}` - -- cgit v1.2.3