From 380613cdb10d15128df78159450efdb2518d247c Mon Sep 17 00:00:00 2001 From: Yuanbin Chen Date: Fri, 27 Jul 2018 16:22:57 +0800 Subject: [PATCH] Fix configure-service-account doc set permissions link error (#9653) Issuse record: #9650 Signed-off-by: Yuanbin.Chen --- .../tasks/configure-pod-container/configure-service-account.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/configure-pod-container/configure-service-account.md b/content/en/docs/tasks/configure-pod-container/configure-service-account.md index 23fc4cf77702f..68bf365e05ff3 100644 --- a/content/en/docs/tasks/configure-pod-container/configure-service-account.md +++ b/content/en/docs/tasks/configure-pod-container/configure-service-account.md @@ -121,7 +121,7 @@ secrets: then you will see that a token has automatically been created and is referenced by the service account. -You may use authorization plugins to [set permissions on service accounts](docs/reference/access-authn-authz/authorization/#service-account-permissions). +You may use authorization plugins to [set permissions on service accounts](docs/reference/access-authn-authz/rbac/#service-account-permissions). To use a non-default service account, simply set the `spec.serviceAccountName` field of a pod to the name of the service account you wish to use.