OSDOCS-14994: updates for mounting secrets section in SSCSI

Author: aravipra

modules/secrets-store-aws.adoc

@@ -15,22 +15,22 @@ endif::[]
 [id="secrets-store-aws_{context}"]
 = Mounting secrets from {secrets-store-provider}
 
-You can use the {secrets-store-operator} to mount secrets from {secrets-store-provider} to a Container Storage Interface (CSI) volume in {product-title}. To mount secrets from {secrets-store-provider}, your cluster must be installed on AWS and use AWS Security Token Service (STS).
+You can use the {secrets-store-operator} to mount secrets from {secrets-store-provider} external secrets store to a Container Storage Interface (CSI) volume in {product-title}. To mount secrets from {secrets-store-provider}, your cluster must be installed on Amazon Web Services (AWS) and use AWS Security Token Service (STS).
 
 .Prerequisites
 
-* Your cluster is installed on AWS and uses AWS Security Token Service (STS).
-* You installed the {secrets-store-operator}. See _Installing the {secrets-store-driver}_ for instructions.
-* You configured {secrets-store-provider} to store the required secrets.
-* You extracted and prepared the `ccoctl` binary.
-* You installed the `jq` CLI tool.
+* You have installed the cluster on AWS and use AWS Security Token Service (STS).
+* You have installed the {secrets-store-operator}. For more information, see "Installing the {secrets-store-driver}".
+* You have configured {secrets-store-provider} to store the required secrets.
+* You have extracted and prepared the `ccoctl` binary.
+* You have installed the `jq` CLI tool.
 * You have access to the cluster as a user with the `cluster-admin` role.
 
 .Procedure
 
 . Install the {secrets-store-provider} provider:
 
-.. Create a YAML file with the following configuration for the provider resources:
+.. Create a YAML file with the following provider resource configurations:
 +
 [IMPORTANT]
 ====
@@ -157,7 +157,7 @@ $ oc apply -f aws-provider.yaml
 $ mkdir credentialsrequest-dir-aws
 ----
 
-.. Create a YAML file with the following configuration for the credentials request:
+.. Create a YAML file with the following credentials request configurations:
 +
 .Example `credentialsrequest.yaml` file
 [source,yaml]
@@ -312,7 +312,7 @@ spec:
             driver: secrets-store.csi.k8s.io
             readOnly: true
             volumeAttributes:
-              secretProviderClass: "my-aws-provider" <3>
+              secretProviderClass: "my-aws-provider"  <3>
 ----
 <1> Specify the name for the deployment.
 <2> Specify the namespace for the deployment. This must be the same namespace as the secret provider class.

modules/secrets-store-azure.adoc

@@ -6,21 +6,21 @@
 [id="secrets-store-azure_{context}"]
 = Mounting secrets from Azure Key Vault
 
-You can use the {secrets-store-operator} to mount secrets from Azure Key Vault to a Container Storage Interface (CSI) volume in {product-title}. To mount secrets from Azure Key Vault, your cluster must be installed on Microsoft Azure.
+You can use the {secrets-store-operator} to mount secrets from Azure Key Vault external secrets store to a Container Storage Interface (CSI) volume in {product-title}. To mount secrets from Azure Key Vault, your cluster must be installed on Microsoft Azure.
 
 .Prerequisites
 
-* Your cluster is installed on Azure.
-* You installed the {secrets-store-operator}. See _Installing the {secrets-store-driver}_ for instructions.
-* You configured Azure Key Vault to store the required secrets.
-* You installed the Azure CLI (`az`).
+* Your have installed the cluster on Azure.
+* You have installed the {secrets-store-operator}. For more information, see "Installing the {secrets-store-driver}".
+* You have configured Azure Key Vault to store the required secrets.
+* You have installed the Azure CLI (`az`) tool.
 * You have access to the cluster as a user with the `cluster-admin` role.
 
 .Procedure
 
 . Install the Azure Key Vault provider:
 
-.. Create a YAML file with the following configuration for the provider resources:
+.. Create a YAML file with the following provider resources configuration:
 +
 [IMPORTANT]
 ====

modules/secrets-store-google.adoc

@@ -6,20 +6,20 @@
 [id="secrets-store-google_{context}"]
 = Mounting secrets from Google Secret Manager
 
-You can use the {secrets-store-operator} to mount secrets from Google Secret Manager to a Container Storage Interface (CSI) volume in {product-title}. To mount secrets from Google Secret Manager, your cluster must be installed on {gcp-first}.
+You can use the {secrets-store-operator} to mount secrets from Google Secret Manager external secrets store to a Container Storage Interface (CSI) volume in {product-title}. To mount secrets from Google Secret Manager, your cluster must be installed on {gcp-first}.
 
 .Prerequisites
 
-* You installed the {secrets-store-operator}. See _Installing the {secrets-store-driver}_ for instructions.
-* You configured Google Secret Manager to store the required secrets.
-* You created a service account key named `key.json` from your Google Cloud service account.
+* You have installed the {secrets-store-operator}. For more information, see "Installing the {secrets-store-driver}".
+* You have configured Google Secret Manager to store the required secrets.
+* You have created a service account key named `key.json` from your Google Cloud service account.
 * You have access to the cluster as a user with the `cluster-admin` role.
 
 .Procedure
 
 . Install the Google Secret Manager provider:
 
-.. Create a YAML file with the following configuration for the provider resources:
+.. Create a YAML file with the following provider resources configuration:
 +
 .Example `gcp-provider.yaml` file
 [source,yaml]

modules/secrets-store-vault.adoc

@@ -6,7 +6,7 @@
 [id="secrets-store-vault_{context}"]
 = Mounting secrets from HashiCorp Vault
 
-You can use the {secrets-store-operator} to mount secrets from HashiCorp Vault to a Container Storage Interface (CSI) volume in {product-title}.
+You can use the {secrets-store-operator} to mount secrets from HashiCorp Vault external secrets store to a Container Storage Interface (CSI) volume in {product-title}.
 
 [IMPORTANT]
 ====
@@ -20,8 +20,8 @@ Other cloud providers might work, but have not been tested yet. Additional cloud
 
 .Prerequisites
 
-* You installed the {secrets-store-operator}. See _Installing the {secrets-store-driver}_ for instructions.
-* You installed Helm.
+* You have installed the {secrets-store-operator}. For more information, see "Installing the {secrets-store-driver}".
+* You installed the Helm package manager.
 * You have access to the cluster as a user with the `cluster-admin` role.
 
 .Procedure
@@ -228,42 +228,6 @@ $ oc exec -i vault-0 --namespace=vault -- vault write auth/kubernetes/role/csi \
 Success! Data written to: auth/kubernetes/role/csi
 ----
 
-.. Verify that all of the `vault` pods are running properly by running the following command:
-+
-[source,terminal]
-----
-$ oc get pods -n vault
-----
-+
-.Example output
-[source,terminal]
-----
-NAME                       READY   STATUS    RESTARTS   AGE
-vault-0                    1/1     Running   0          43m
-vault-csi-provider-87rgw   2/2     Running   0          19m
-vault-csi-provider-bd6hp   2/2     Running   0          19m
-vault-csi-provider-smlv7   2/2     Running   0          19m
-----
-
-.. Verify that all of the `secrets-store-csi-driver` pods are running properly by running the following command:
-+
-[source,terminal]
-----
-$ oc get pods -n openshift-cluster-csi-drivers | grep -E "secrets"
-----
-+
-.Example output
-[source,terminal]
-----
-secrets-store-csi-driver-node-46d2g                  3/3     Running   0             45m
-secrets-store-csi-driver-node-d2jjn                  3/3     Running   0             45m
-secrets-store-csi-driver-node-drmt4                  3/3     Running   0             45m
-secrets-store-csi-driver-node-j2wlt                  3/3     Running   0             45m
-secrets-store-csi-driver-node-v9xv4                  3/3     Running   0             45m
-secrets-store-csi-driver-node-vlz28                  3/3     Running   0             45m
-secrets-store-csi-driver-operator-84bd699478-fpxrw   1/1     Running   0             47m
-----
-
 . Create a secret provider class to define your secrets store provider:
 
 .. Create a YAML file that defines the `SecretProviderClass` object:
@@ -355,7 +319,43 @@ $ oc create -f deployment.yaml
 
 .Verification
 
-* Verify that you can access the secrets from your HashiCorp Vault in the pod volume mount:
+. Verify that all of the `vault` pods are running properly by running the following command:
++
+[source,terminal]
+----
+$ oc get pods -n vault
+----
++
+.Example output
+[source,terminal]
+----
+NAME                       READY   STATUS    RESTARTS   AGE
+vault-0                    1/1     Running   0          43m
+vault-csi-provider-87rgw   2/2     Running   0          19m
+vault-csi-provider-bd6hp   2/2     Running   0          19m
+vault-csi-provider-smlv7   2/2     Running   0          19m
+----
+
+. Verify that all of the `secrets-store-csi-driver` pods are running properly by running the following command:
++
+[source,terminal]
+----
+$ oc get pods -n openshift-cluster-csi-drivers | grep -E "secrets"
+----
++
+.Example output
+[source,terminal]
+----
+secrets-store-csi-driver-node-46d2g                  3/3     Running   0             45m
+secrets-store-csi-driver-node-d2jjn                  3/3     Running   0             45m
+secrets-store-csi-driver-node-drmt4                  3/3     Running   0             45m
+secrets-store-csi-driver-node-j2wlt                  3/3     Running   0             45m
+secrets-store-csi-driver-node-v9xv4                  3/3     Running   0             45m
+secrets-store-csi-driver-node-vlz28                  3/3     Running   0             45m
+secrets-store-csi-driver-operator-84bd699478-fpxrw   1/1     Running   0             47m
+----
+
+. Verify that you can access the secrets from your HashiCorp Vault in the pod volume mount:
 
 .. List the secrets in the pod mount by running the following command:
 +