Skip to content

Commit 816cef4

Browse files
authored
Describe the dws-workload-manager ClusterRole for the WLM (#150)
Signed-off-by: Dean Roehrich <dean.roehrich@hpe.com>
1 parent 52d2287 commit 816cef4

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

docs/guides/rbac-for-users/readme.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -125,15 +125,15 @@ Generate a key and certificate for our "flux" user, similar to the way we create
125125

126126
After the keys have been generated, a new kubeconfig file can be created for the "flux" user, similar to the one for the "hpe" user above. Again, substitute "flux" in place of "hpe".
127127

128-
### Apply the provided ClusterRole and create a ClusterRoleBinding
128+
### Use the provided ClusterRole and create a ClusterRoleBinding
129129

130-
DataWorkflowServices has already defined the role to be used with WLMs. Simply apply the `workload-manager` ClusterRole from DataWorkflowServices to the system:
130+
DataWorkflowServices has already defined the role to be used with WLMs, named `dws-workload-manager`:
131131

132132
```console
133-
kubectl apply -f https://github.com/DataWorkflowServices/dws/raw/master/config/rbac/workload_manager_role.yaml
133+
kubectl get clusterrole dws-workload-manager
134134
```
135135

136-
Create and apply a ClusterRoleBinding to associate the "flux" user with the `workload-manager` ClusterRole:
136+
Create and apply a ClusterRoleBinding to associate the "flux" user with the `dws-workload-manager` ClusterRole:
137137

138138
ClusterRoleBinding
139139
```yaml

0 commit comments

Comments
 (0)