File tree Expand file tree Collapse file tree 1 file changed +4
-3
lines changed
content/en/docs/reference/using-api Expand file tree Collapse file tree 1 file changed +4
-3
lines changed Original file line number Diff line number Diff line change @@ -87,14 +87,15 @@ Currently, there are several API groups in use:
87
87
* The named groups are at REST path ` /apis/$GROUP_NAME/$VERSION ` and use
88
88
` apiVersion: $GROUP_NAME/$VERSION ` (for example, ` apiVersion: batch/v1 ` ).
89
89
You can find the full list of supported API groups in
90
- [ Kubernetes API reference] (/docs/reference/generated/kubernetes-api/{{< param "version" >}}/).
90
+ [ Kubernetes API reference] (/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#-strong-api-groups-strong- ).
91
91
92
92
## Enabling or disabling API groups {#enabling-or-disabling}
93
93
94
94
Certain resources and API groups are enabled by default. You can enable or
95
95
disable them by setting ` --runtime-config ` on the API server. The
96
- ` --runtime-config ` flag accepts comma separated ` <key>=<value> ` pairs
97
- describing the runtime configuration of the API server. For example:
96
+ ` --runtime-config ` flag accepts comma separated ` <key>[=<value>] ` pairs
97
+ describing the runtime configuration of the API server. If the ` =<value> `
98
+ part is omitted, it is treated as if ` =true ` is specified. For example:
98
99
99
100
- to disable ` batch/v1 ` , set ` --runtime-config=batch/v1=false `
100
101
- to enable ` batch/v2alpha1 ` , set ` --runtime-config=batch/v2alpha1 `
You can’t perform that action at this time.
0 commit comments