From 1f7f8dcb7c10c46fde62a217cc25ac43bfadffd9 Mon Sep 17 00:00:00 2001 From: Yuvraj Mehta <29581448+moscowrage@users.noreply.github.com> Date: Fri, 7 Sep 2018 12:18:17 -0700 Subject: [PATCH 1/2] Update congigure-rbac-kube.md --- ee/ucp/authorization/congigure-rbac-kube.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ee/ucp/authorization/congigure-rbac-kube.md b/ee/ucp/authorization/congigure-rbac-kube.md index 044e4b381f..8147c455df 100644 --- a/ee/ucp/authorization/congigure-rbac-kube.md +++ b/ee/ucp/authorization/congigure-rbac-kube.md @@ -22,7 +22,7 @@ To create a Kuberenetes roles in the UCP web interface: 1. Go to the UCP web UI. 2. Navigate to the **Access Control**. -3. In the lefthand menu, select **Roles**. +3. In the lefthand menu, select **Users**. ![Kubernetes Grants in UCP](../images/kube-rbac-roles.png) From 82402c79bff93325f22d1ef321e029e6f78c4732 Mon Sep 17 00:00:00 2001 From: Yuvraj Mehta <29581448+moscowrage@users.noreply.github.com> Date: Fri, 7 Sep 2018 12:52:53 -0700 Subject: [PATCH 2/2] Update congigure-rbac-kube.md --- ee/ucp/authorization/congigure-rbac-kube.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/ee/ucp/authorization/congigure-rbac-kube.md b/ee/ucp/authorization/congigure-rbac-kube.md index 8147c455df..c4acdff1ae 100644 --- a/ee/ucp/authorization/congigure-rbac-kube.md +++ b/ee/ucp/authorization/congigure-rbac-kube.md @@ -12,7 +12,7 @@ UCP 3.0 used its own role-based asccess control (RBAC) for Kubernetes clusters. Kubernetes RBAC is turned on by default when customers upgrade to UCP 3.1. See [RBAC authorization in Kubernetes](https://v1-8.docs.kubernetes.io/docs/admin/authorization/rbac/) for more information about Kubernetes. -Starting with UCP 3.1, Kubernetes & Swarm roles have separate views. You can view all the roles for a particular cluster under **Access Control** then **Users**. Select Kubernetes or Swarm to view the specific roles for each. +Starting with UCP 3.1, Kubernetes & Swarm roles have separate views. You can view all the roles for a particular cluster under **Access Control** then **Roles**. Select Kubernetes or Swarm to view the specific roles for each. ## Creating roles @@ -32,6 +32,8 @@ To create a Kuberenetes roles in the UCP web interface: ![Kubernetes Role Creation in UCP](../images/kube-role-create.png) 6. Select a namespace from the **Namespace** dropdown list. + Selecting a specific **Namespace** will create a `Role` for use within that namespace only. + Selecting **All NameSpaces** will create a `ClusterRole` which can be used to create rules for cluster and namespace scoped Kubernetes resources 7. Provide the YAML for the role, either by entering it in the **Object YAML** editor or select **Click to upload a .yml file** to choose and upload a .yml file instead. 8. When you have finished specifying the YAML, Select **Create** to complete role creation. @@ -41,7 +43,7 @@ To create a Kuberenetes roles in the UCP web interface: Kubernetes provides 2 types of role grants: - `ClusterRoleBinding` which applies to all namespaces -- `RoleBinding1` which applies to a specific namespace +- `RoleBinding` which applies to a specific namespace To create a grant for a Kuberenetes role in the UCP web interface: