Fixes the second issue in the Dead Link Report: broken URL in docs/admin/authorization
This commit is contained in:
@@ -204,7 +204,7 @@ As of 1.3 RBAC mode is in alpha and considered experimental.
|
||||
|
||||
To use RBAC, you must both enable the authorization module with `--authorization-mode=RBAC`,
|
||||
and [enable the API version](
|
||||
docs/admin/cluster-management.md/#Turn-on-or-off-an-api-version-for-your-cluster),
|
||||
../cluster-management.md/#Turn-on-or-off-an-api-version-for-your-cluster),
|
||||
with a `--runtime-config=` that includes `rbac.authorization.k8s.io/v1alpha1`.
|
||||
|
||||
### Roles, RolesBindings, ClusterRoles, and ClusterRoleBindings
|
||||
|
||||
@@ -170,7 +170,7 @@ This is an infrequent event, but it requires careful management. There is a sequ
|
||||
1. Turn off the old API version.
|
||||
|
||||
### Turn on or off an API version for your cluster
|
||||
|
||||
<a name="Turn-on-or-off-an-api-version-for-your-cluster"></a>
|
||||
Specific API versions can be turned on or off by passing --runtime-config=api/<version> flag while bringing up the API server. For example: to turn off v1 API, pass `--runtime-config=api/v1=false`.
|
||||
runtime-config also supports 2 special keys: api/all and api/legacy to control all and legacy APIs respectively.
|
||||
For example, for turning off all api versions except v1, pass `--runtime-config=api/all=false,api/v1=true`.
|
||||
|
||||
Reference in New Issue
Block a user