Skip to content

Commit aad7c73

Browse files
authored
Merge pull request #53597 from intojhanurag/docs/feature-gates-mention-flagz
docs: mention /flagz for feature gate verification
2 parents d41cc34 + 4bfe30b commit aad7c73

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

content/en/docs/tasks/administer-cluster/configure-feature-gates.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -219,6 +219,19 @@ In kubeadm clusters, verify all relevant locations where feature gates might be
219219
configured, as the configuration is distributed across multiple files and locations.
220220
{{< /note >}}
221221

222+
### Check via /flagz endpoint
223+
224+
If you have access to a component's debugging endpoints, and the `ComponentFlagz`
225+
feature gate is enabled for that component, you can inspect the command-line flags
226+
that were used to start the component by visiting the `/flagz` endpoint. Feature
227+
gates configured using command-line flags appear in this output.
228+
229+
The `/flagz` endpoint is part of Kubernetes *z-pages*, which provide human-readable
230+
runtime debugging information for core components.
231+
232+
For more information, see the
233+
[z-pages documentation](/docs/reference/instrumentation/zpages/).
234+
222235
## Understanding component-specific requirements
223236

224237
Some examples of component-specific feature gates:

0 commit comments

Comments
 (0)