1
1
////
2
2
create aggregated cluster role definitions for a custom resource definition
3
3
4
- This module contains xrefs. If you need to reuse it, make sure the links work
5
- in your assembly. You might need to add a conditional statement to place the
6
- right link for your assembly.
7
-
8
4
Module included in the following assemblies:
9
5
10
6
* admin_guide/custom_resource_definitions.adoc
@@ -15,7 +11,7 @@ Module included in the following assemblies:
15
11
16
12
After you create cluster-scoped CRDs, you can grant permissions to it. If you
17
13
use the admin, edit, and view
18
- xref:../ architecture/additional_concepts/authorization.adoc#roles[default
14
+ xref:architecture/additional_concepts/authorization.adoc#roles[default
19
15
cluster roles], take advantage of cluster role aggregation for their rules.
20
16
21
17
[IMPORTANT]
@@ -26,7 +22,7 @@ assign a rule to a role, you must also assign that verb to roles that have more
26
22
permissions. For example, if you grant the "get crontabs" permission to the view
27
23
role, you must also grant it to the edit and admin roles. The admin or edit role
28
24
is usually assigned to the user that created a project through the
29
- xref:../ admin_guide/managing_projects.adoc#modifying-the-template-for-new-projects[project
25
+ xref:admin_guide/managing_projects.adoc#modifying-the-template-for-new-projects[project
30
26
template].
31
27
====
32
28
70
66
<4> Specify this label to grant permissions to the edit default role.
71
67
<5> Specify the group name of the CRD.
72
68
<6> Specify the plural name of the CRD that these rules apply to.
73
- <7> Specify the xref:../ architecture/additional_concepts/authorization.adoc#action[verbs]
69
+ <7> Specify the xref:architecture/additional_concepts/authorization.adoc#action[verbs]
74
70
that represent the permissions that are granted to the role. For example, apply
75
71
read and write permissions to the admin and edit roles and only read permission
76
72
to the view role.
0 commit comments