Skip to content

Commit e9d32b4

Browse files
committed
OSDOCS#10927: Adding support for secrets store with GCP
1 parent ee42877 commit e9d32b4

File tree

6 files changed

+334
-22
lines changed

6 files changed

+334
-22
lines changed

modules/secrets-store-aws.adoc

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -15,15 +15,15 @@ endif::[]
1515
[id="secrets-store-aws_{context}"]
1616
= Mounting secrets from {secrets-store-provider}
1717

18-
You can use the {secrets-store-operator} to mount secrets from {secrets-store-provider} to a 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).
18+
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).
1919

2020
.Prerequisites
2121

2222
* Your cluster is installed on AWS and uses AWS Security Token Service (STS).
23-
* You have installed the {secrets-store-operator}. See _Installing the {secrets-store-driver}_ for instructions.
24-
* You have configured {secrets-store-provider} to store the required secrets.
25-
* You have extracted and prepared the `ccoctl` binary.
26-
* You have installed the `jq` CLI tool.
23+
* You installed the {secrets-store-operator}. See _Installing the {secrets-store-driver}_ for instructions.
24+
* You configured {secrets-store-provider} to store the required secrets.
25+
* You extracted and prepared the `ccoctl` binary.
26+
* You installed the `jq` CLI tool.
2727
* You have access to the cluster as a user with the `cluster-admin` role.
2828
2929
.Procedure
@@ -328,11 +328,11 @@ $ oc create -f deployment.yaml
328328

329329
* Verify that you can access the secrets from {secrets-store-provider} in the pod volume mount:
330330
331-
.. List the secrets in the pod mount:
331+
.. List the secrets in the pod mount by running the following command:
332332
+
333333
[source,terminal]
334334
----
335-
$ oc exec busybox-<hash> -n my-namespace -- ls /mnt/secrets-store/
335+
$ oc exec my-aws-deployment-<hash> -n my-namespace -- ls /mnt/secrets-store/
336336
----
337337
+
338338
.Example output
@@ -346,11 +346,11 @@ testParameter
346346
endif::aws-systems-manager-parameter-store[]
347347
----
348348

349-
.. View a secret in the pod mount:
349+
.. View a secret in the pod mount by running the following command:
350350
+
351351
[source,terminal]
352352
----
353-
$ oc exec busybox-<hash> -n my-namespace -- cat /mnt/secrets-store/testSecret
353+
$ oc exec my-aws-deployment-<hash> -n my-namespace -- cat /mnt/secrets-store/testSecret
354354
----
355355
+
356356
.Example output

modules/secrets-store-azure.adoc

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -6,14 +6,14 @@
66
[id="secrets-store-azure_{context}"]
77
= Mounting secrets from Azure Key Vault
88

9-
You can use the {secrets-store-operator} to mount secrets from Azure Key Vault to a CSI volume in {product-title}. To mount secrets from Azure Key Vault, your cluster must be installed on Microsoft Azure.
9+
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.
1010

1111
.Prerequisites
1212

1313
* Your cluster is installed on Azure.
14-
* You have installed the {secrets-store-operator}. See _Installing the {secrets-store-driver}_ for instructions.
15-
* You have configured Azure Key Vault to store the required secrets.
16-
* You have installed the Azure CLI (`az`).
14+
* You installed the {secrets-store-operator}. See _Installing the {secrets-store-driver}_ for instructions.
15+
* You configured Azure Key Vault to store the required secrets.
16+
* You installed the Azure CLI (`az`).
1717
* You have access to the cluster as a user with the `cluster-admin` role.
1818
1919
.Procedure
@@ -283,11 +283,11 @@ $ oc create -f deployment.yaml
283283

284284
* Verify that you can access the secrets from Azure Key Vault in the pod volume mount:
285285
286-
.. List the secrets in the pod mount:
286+
.. List the secrets in the pod mount by running the following command:
287287
+
288288
[source,terminal]
289289
----
290-
$ oc exec busybox-<hash> -n my-namespace -- ls /mnt/secrets-store/
290+
$ oc exec my-azure-deployment-<hash> -n my-namespace -- ls /mnt/secrets-store/
291291
----
292292
+
293293
.Example output
@@ -296,11 +296,11 @@ $ oc exec busybox-<hash> -n my-namespace -- ls /mnt/secrets-store/
296296
secret1
297297
----
298298

299-
.. View a secret in the pod mount:
299+
.. View a secret in the pod mount by running the following command:
300300
+
301301
[source,terminal]
302302
----
303-
$ oc exec busybox-<hash> -n my-namespace -- cat /mnt/secrets-store/secret1
303+
$ oc exec my-azure-deployment-<hash> -n my-namespace -- cat /mnt/secrets-store/secret1
304304
----
305305
+
306306
.Example output

0 commit comments

Comments
 (0)