Browse Source

Update full-cluster-secret-store example to reference secret namespaces (#4964)

The example as written doesn't work if you're trying to create an external secret in any namespace other than the one with your AWS access key secrets in it. We should specify the namespace of the secrets in the ClusterSecretStore example so that it actually works for people following along when creating ExternalSecrets in another namespace that reference the cluster-wide store.

Signed-off-by: Jaz <ericvolp12@gmail.com>
Co-authored-by: Gergely Brautigam <182850+Skarlso@users.noreply.github.com>
Jaz 9 months ago
parent
commit
14737f32a2
1 changed files with 2 additions and 0 deletions
  1. 2 0
      docs/snippets/full-cluster-secret-store.yaml

+ 2 - 0
docs/snippets/full-cluster-secret-store.yaml

@@ -28,9 +28,11 @@ spec:
         # Getting the accessKeyID and secretAccessKey from an already created Kubernetes Secret
         secretRef:
           accessKeyIDSecretRef:
+            namespace: external-secrets
             name: awssm-secret
             key: access-key
           secretAccessKeySecretRef:
+            namespace: external-secrets
             name: awssm-secret
             key: secret-access-key
         # IAM roles for service accounts