Provision Azure Files ReadWriteMany Persistent Volumes on Azure OpenShift: Difference between revisions
Jump to navigation
Jump to search
Line 14: | Line 14: | ||
Assign the role: | Assign the role: | ||
<syntaxhighlight lang='bash'> | <syntaxhighlight lang='bash'> | ||
az role assignment create | az role assignment create --role Contributor --assignee <openshift-cluster-service-principal> -g <openshift-cluster-resource-group> | ||
</syntaxhighlight> | </syntaxhighlight> | ||
For more details about role assignment see: {{Internal|Azure_Security_Operations#Assign_a_Role|Azure Security Operations | Assign a Role}} | For more details about role assignment see: {{Internal|Azure_Security_Operations#Assign_a_Role|Azure Security Operations | Assign a Role}} |
Revision as of 20:53, 25 November 2020
External
Internal
Procedure
1. Create a storage account with its dedicated resource group. Why? Why can't we use the OpenShift cluster resource group?. Use this:
2. Give the OpenShift service principal "listKey" permission on the new storage account resource group. Assign the "Contributor" role to achieve this.
The OpenShift service principal can be obtained as described here:
Assign the role:
az role assignment create --role Contributor --assignee <openshift-cluster-service-principal> -g <openshift-cluster-resource-group>
For more details about role assignment see: