public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-17 18:37:03 +00:00
Code Issues Packages Projects Releases Wiki Activity

adding description of custom resource

Browse Source
This commit is contained in:
Mark Bishop
2018-10-02 18:00:57 -07:00
parent b87081a48c
commit b432bcb4de
3 changed files with 16 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/admin-settings/rbac/cluster-project-roles/_index.md
+9 -2
View File
@@ -43,7 +43,10 @@ The following table lists each built-in custom cluster role available in Rancher
| View Cluster Members | ✓ | ✓ |
| View Nodes | ✓ | ✓ |
> **Note:** Each cluster role listed above, including `Owner` and `Member`, is comprised of multiple rules granting access to various resources. You can view the roles and their rules on the Global > Security > Roles page.
> **Notes:**
>
>- Each cluster role listed above, including `Owner` and `Member`, is comprised of multiple rules granting access to various resources. You can view the roles and their rules on the Global > Security > Roles page.
>- Resources denoted with `(Custom)` are resources defined by the Rancher API—_not_ Kubernetes.
### Project Roles
@@ -94,7 +97,11 @@ The following table lists each built-in custom project role available in Rancher
| View Volumes | ✓ | ✓ | ✓ |
| View Workloads | ✓ | ✓ | ✓ |
> **Note:** Each project role listed above, including Owner, Member, and Read Only, is comprised of multiple rules granting access to various resources. You can view the roles and their rules on the Global > Security > Roles page.
> **Notes:**
>
>- Each project role listed above, including `Owner`, `Member`, and `Read Only`, is comprised of multiple rules granting access to various resources. You can view the roles and their rules on the Global > Security > Roles page.
>- Resources denoted with `(Custom)` are resources defined by the Rancher API—_not_ Kubernetes.
### Defining Custom Roles
As previously mentioned, custom roles can be defined for use at the cluster or project level. The context field defines whether the role will appear on the cluster member page, project member page, or both.
content/rancher/v2.x/en/admin-settings/rbac/default-custom-roles/_index.md
+2
View File
@@ -62,6 +62,8 @@ While Rancher comes out-of-the-box with a set of default user roles, you can als
6. Use the **Grant Resources** options to assign individual [Kubernetes API endpoints](https://kubernetes.io/docs/reference/) to the role.
>**Note**: Resources denoted with `(Custom)` are resources defined by the Rancher API—_not_ Kubernetes.
You can also choose the individual cURL methods (`Create`, `Delete`, `Get`, etc.) available for use with each endpoint you assign.
7. Use the **Inherit from a Role** options to assign individual Rancher roles to your custom roles.
content/rancher/v2.x/en/admin-settings/rbac/global-permissions/_index.md
+5 -1
View File
@@ -51,7 +51,11 @@ The following table lists each custom global permission available and whether it
| User Catalog Templates | ✓ | ✓ |
| Login Access | ✓ | ✓ |
> **Note:** Each permission listed above is comprised of multiple individual permissions not listed in the Rancher UI. For a full list of these permissions and the rules they are comprised of, access through the API at `/v3/globalroles`.
> **Note:**
>
>- Each permission listed above is comprised of multiple individual permissions not listed in the Rancher UI. For a full list of these permissions and the rules they are comprised of, access through the API at `/v3/globalRoles`.
>- Resources denoted with `(Custom)` are resources defined by the Rancher API—_not_ Kubernetes.
### Default Global Permissions for New Users