Update authentication links (#9452)
* update authentication links * undo cn updates
This commit is contained in:
@@ -102,7 +102,7 @@ You (or your {{< glossary_tooltip text="cluster operator" term_id="cluster-opera
|
||||
|
||||
For even more comprehensive reading about security best practices, consider checking out the following topics:
|
||||
|
||||
* {{< link text="Authentication" url="/docs/admin/authentication/" >}} (Is the user who they say they are?)
|
||||
* {{< link text="Authentication" url="/docs/reference/access-authn-authz/authentication/" >}} (Is the user who they say they are?)
|
||||
* {{< link text="Authorization" url="/docs/admin/authorization/" >}} (Does the user actually have permissions to do what they're asking?)
|
||||
|
||||
#### Resource isolation and management
|
||||
|
||||
@@ -60,7 +60,7 @@ Securing your cluster includes work beyond the scope of Kubernetes itself.
|
||||
In Kubernetes, you configure access control:
|
||||
|
||||
* [Controlling Access to the Kubernetes API](/docs/admin/accessing-the-api/)
|
||||
* [Authenticating](/docs/admin/authentication/)
|
||||
* [Authenticating](/docs/reference/access-authn-authz/authentication/)
|
||||
* [Using Admission Controllers](/docs/admin/admission-controllers/)
|
||||
|
||||
You also configure authorization. That is, you determine not just how users and services authenticate to the API server, or whether they have access, but also what resources they have access to. Role-based access control (RBAC) is the recommended mechanism for controlling authorization to Kubernetes resources. Other authorization modes are available for more specific use cases.
|
||||
|
||||
Reference in New Issue
Block a user