fix typos in /admin/authorization/rbac.md (#5427)

This commit is contained in:
Weibin Lin
2017-09-14 06:40:32 +08:00
committed by Steve Perry
parent c8adeb0154
commit 34d2a2e7f2
+2 -2
View File
@@ -102,7 +102,7 @@ This allows administrators to define a set of common roles for the entire cluste
then reuse them within multiple namespaces. then reuse them within multiple namespaces.
For instance, even though the following `RoleBinding` refers to a `ClusterRole`, For instance, even though the following `RoleBinding` refers to a `ClusterRole`,
"dave" (the subject) will only be able read secrets in the "development" "dave" (the subject) will only be able to read secrets in the "development"
namespace (the namespace of the `RoleBinding`). namespace (the namespace of the `RoleBinding`).
```yaml ```yaml
@@ -258,7 +258,7 @@ A `RoleBinding` or `ClusterRoleBinding` binds a role to *subjects*.
Subjects can be groups, users or service accounts. Subjects can be groups, users or service accounts.
Users are represented by strings. These can be plain usernames, like Users are represented by strings. These can be plain usernames, like
"alice", email-style names, like "bob@example.com", or numeric ids "alice", email-style names, like "bob@example.com", or numeric IDs
represented as a string. It is up to the Kubernetes admin to configure represented as a string. It is up to the Kubernetes admin to configure
the [authentication modules](/docs/admin/authentication/) to produce the [authentication modules](/docs/admin/authentication/) to produce
usernames in the desired format. The RBAC authorization system does usernames in the desired format. The RBAC authorization system does