update service-accounts-admin links (#9461)
This commit is contained in:
@@ -44,7 +44,7 @@ or static Bearer token approach. Larger clusters may wish to integrate an existi
|
||||
allow users to be subdivided into groups.
|
||||
|
||||
All API clients must be authenticated, even those that are part of the infrastructure like nodes,
|
||||
proxies, the scheduler, and volume plugins. These clients are typically [service accounts](/docs/admin/service-accounts-admin/) or use x509 client certificates, and they are created automatically at cluster startup or are setup as part of the cluster installation.
|
||||
proxies, the scheduler, and volume plugins. These clients are typically [service accounts](/docs/reference/access-authn-authz/service-accounts-admin/) or use x509 client certificates, and they are created automatically at cluster startup or are setup as part of the cluster installation.
|
||||
|
||||
Consult the [authentication reference document](/docs/reference/access-authn-authz/authentication/) for more information.
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ weight: 90
|
||||
A service account provides an identity for processes that run in a Pod.
|
||||
|
||||
*This is a user introduction to Service Accounts. See also the
|
||||
[Cluster Admin Guide to Service Accounts](/docs/admin/service-accounts-admin/).*
|
||||
[Cluster Admin Guide to Service Accounts](/docs/reference/access-authn-authz/service-accounts-admin/).*
|
||||
|
||||
{{< note >}}
|
||||
**Note:** This document describes how service accounts behave in a cluster set up
|
||||
|
||||
Reference in New Issue
Block a user