Skip to content

Commit 526f61e

Browse files
authored
Merge pull request #35309 from yanrongshi/zh-cn]sync-access-authn-authz/rbac
[zh-cn]sync rbac.md
2 parents 536a524 + 697c6de commit 526f61e

File tree

1 file changed

+7
-7
lines changed
  • content/zh-cn/docs/reference/access-authn-authz

1 file changed

+7
-7
lines changed

content/zh-cn/docs/reference/access-authn-authz/rbac.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -64,8 +64,8 @@ or amend them, using tools such as `kubectl`, just like any other Kubernetes obj
6464
-->
6565
## API 对象 {#api-overview}
6666

67-
RBAC API 声明了四种 Kubernetes 对象:_Role__ClusterRole__RoleBinding_
68-
_ClusterRoleBinding_。你可以像使用其他 Kubernetes 对象一样,通过类似 `kubectl`
67+
RBAC API 声明了四种 Kubernetes 对象:**Role****ClusterRole****RoleBinding**
68+
**ClusterRoleBinding**。你可以像使用其他 Kubernetes 对象一样,通过类似 `kubectl`
6969
这类工具[描述对象](/zh-cn/docs/concepts/overview/working-with-objects/kubernetes-objects/#understanding-kubernetes-objects),
7070
或修补对象。
7171

@@ -96,7 +96,7 @@ it can't be both.
9696
-->
9797
### Role 和 ClusterRole {#role-and-clusterole}
9898

99-
RBAC 的 _Role__ClusterRole_ 中包含一组代表相关权限的规则。
99+
RBAC 的 **Role****ClusterRole** 中包含一组代表相关权限的规则。
100100
这些权限是纯粹累加的(不存在拒绝某操作的规则)。
101101

102102
Role 总是用来在某个{{< glossary_tooltip text="名字空间" term_id="namespace" >}}内设置访问权限;
@@ -108,17 +108,17 @@ Role 总是用来在某个{{< glossary_tooltip text="名字空间" term_id="name
108108
<!--
109109
ClusterRoles have several uses. You can use a ClusterRole to:
110110
111-
1. define permissions on namespaced resources and be granted within individual namespace(s)
112-
1. define permissions on namespaced resources and be granted across all namespaces
111+
1. define permissions on namespaced resources and be granted access within individual namespace(s)
112+
1. define permissions on namespaced resources and be granted access across all namespaces
113113
1. define permissions on cluster-scoped resources
114114
115115
If you want to define a role within a namespace, use a Role; if you want to define
116116
a role cluster-wide, use a ClusterRole.
117117
-->
118118
ClusterRole 有若干用法。你可以用它来:
119119

120-
1. 定义对某名字空间域对象的访问权限,并将在各个名字空间内完成授权
121-
1. 为名字空间作用域的对象设置访问权限,并跨所有名字空间执行授权
120+
1. 定义对某名字空间域对象的访问权限,并将在个别名字空间内被授予访问权限
121+
1. 为名字空间作用域的对象设置访问权限,并被授予跨所有名字空间的访问权限
122122
1. 为集群作用域的资源定义访问权限。
123123

124124
如果你希望在名字空间内定义角色,应该使用 Role;

0 commit comments

Comments
 (0)