From fe3032c56e493faffc827d1fd3e90f20a56957eb Mon Sep 17 00:00:00 2001 From: Chao Wang Date: Mon, 17 Dec 2018 12:54:54 +0800 Subject: [PATCH] Improve explanation of feature-gates/component relationship and usage (#11562) --- .../command-line-tools-reference/feature-gates.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) 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 7d665737c3..8d9767a6b5 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 @@ -16,7 +16,14 @@ can specify on different Kubernetes components. Feature gates are a set of key=value pairs that describe alpha or experimental features. An administrator can use the `--feature-gates` command line flag on each component -to turn a feature on or off. +to turn a feature on or off. Each component supports a set of feature gates unique to that component. +Use `-h` flag to see a full set of feature gates for all components. +To set feature gates for a component, such as kubelet, use the `--feature-gates` flag assigned to a list of feature pairs: + +```shell +--feature-gates="...,DynamicKubeletConfig=true" +``` + The following table is a summary of the feature gates that you can set on different Kubernetes components.