whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update authorization-rbac links (#9463)

Browse Source 
* update authorization-rbac links

* fix broken links

* undo modification of cn content
This commit is contained in:
Bob Killen
2018-07-18 18:32:04 -04:00
committed by k8s-ci-robot
parent 76b7f9cb1a
commit 2ee2e9d5bb
11 changed files with 26 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/administer-cluster/securing-a-cluster.md
+3 -2
View File
@@ -51,11 +51,12 @@ Consult the [authentication reference document](/docs/reference/access-authn-aut
### API Authorization
Once authenticated, every API call is also expected to pass an authorization check. Kubernetes ships
an integrated [Role-Based Access Control (RBAC)](/docs/admin/authorization/rbac/) component that matches an incoming user or group to a
an integrated [Role-Based Access Control (RBAC)](/docs/reference/access-authn-authz/rbac/) component that matches an incoming user or group to a
set of permissions bundled into roles. These permissions combine verbs (get, create, delete) with
resources (pods, services, nodes) and can be namespace or cluster scoped. A set of out of the box
roles are provided that offer reasonable default separation of responsibility depending on what
actions a client might want to perform. It is recommended that you use the [Node](/docs/reference/access-authn-authz/node/) and [RBAC](/docs/admin/authorization/rbac/) authorizers together, in combination with the
actions a client might want to perform. It is recommended that you use the [Node](/docs/reference/access-authn-authz/node/)
and [RBAC](/docs/reference/access-authn-authz/rbac/) authorizers together, in combination with the
[NodeRestriction](/docs/admin/admission-controllers/#noderestriction) admission plugin.
As with authentication, simple and broad roles may be appropriate for smaller clusters, but as