Skip to content

Commit 148f3c6

Browse files
committed
acrolinx changes
1 parent 29571f1 commit 148f3c6

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/openshift/howto-create-a-storageclass.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ In this article, you’ll create a StorageClass for Azure Red Hat OpenShift 4 th
1919
> * Setup the prerequisites and install the necessary tools
2020
> * Create an Azure Red Hat OpenShift 4 StorageClass with the Azure File provisioner
2121
22-
If you choose to install and use the CLI locally, this tutorial requires that you are running the Azure CLI version 2.6.0 or later. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI](/cli/azure/install-azure-cli).
22+
If you choose to install and use the CLI locally, this tutorial requires that you're running the Azure CLI version 2.6.0 or later. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI](/cli/azure/install-azure-cli).
2323

2424
## Before you begin
2525

@@ -28,7 +28,7 @@ Deploy an Azure Red Hat OpenShift 4 cluster into your subscription, see [Create
2828

2929
### Set up Azure storage account
3030

31-
This step will create a resource group outside of the Azure Red Hat OpenShift (ARO) cluster’s resource group. This resource group will contain the Azure Files shares that are created by Azure Red Hat OpenShift’s dynamic provisioner.
31+
This step creates a resource group outside of the Azure Red Hat OpenShift (ARO) cluster’s resource group. This resource group contains the Azure Files shares that created Azure Red Hat OpenShift’s dynamic provisioner.
3232

3333
```azurecli
3434
AZURE_FILES_RESOURCE_GROUP=aro_azure_files
@@ -60,7 +60,7 @@ az role assignment create --role Contributor --scope /subscriptions/mySubscripti
6060

6161
### Set ARO cluster permissions
6262

63-
The OpenShift persistent volume binder service account will require the ability to read secrets. Create and assign an OpenShift cluster role to achieve this.
63+
The OpenShift persistent volume binder service account requires the ability to read secrets. Create and assign an OpenShift cluster role to achieve this.
6464
```azurecli
6565
ARO_API_SERVER=$(az aro list --query "[?contains(name,'$CLUSTER')].[apiserverProfile.url]" -o tsv)
6666
@@ -75,9 +75,9 @@ oc adm policy add-cluster-role-to-user azure-secret-reader system:serviceaccount
7575

7676
## Create StorageClass with Azure Files provisioner
7777

78-
This step will create a StorageClass with an Azure Files provisioner. Within the StorageClass manifest, the details of the storage account are required so that the ARO cluster knows to look at a storage account outside of the current resource group.
78+
This step creates a StorageClass with an Azure Files provisioner. Within the StorageClass manifest, the details of the storage account are required so that the ARO cluster knows to look at a storage account outside of the current resource group.
7979

80-
During storage provisioning, a secret named by secretName is created for the mounting credentials. In a multi-tenancy context, it is strongly recommended to set the value for secretNamespace explicitly, otherwise the storage account credentials may be read by other users.
80+
During storage provisioning, a secret named by secretName is created for the mounting credentials. In a multi-tenancy context, it's strongly recommended to set the value for secretNamespace explicitly, otherwise the storage account credentials may be read by other users.
8181

8282
```bash
8383
cat << EOF >> azure-storageclass-azure-file.yaml
@@ -108,7 +108,7 @@ EOF
108108
oc create -f azure-storageclass-azure-file.yaml
109109
```
110110

111-
Mount options for Azure Files will generally be dependent on the workload that you are deploying and the requirements of the application. Specifically for Azure files, there are additional parameters that you should consider using.
111+
Mount options for Azure Files will generally be dependent on the workload that you're deploying and the requirements of the application. Specifically for Azure files, there are other parameters that you should consider using.
112112

113113
Mandatory parameters:
114114
- "mfsymlinks" to map symlinks to a form the client can use

0 commit comments

Comments
 (0)