From a047657efdbfc0ff0f9b70c08c040fae8a3953ed Mon Sep 17 00:00:00 2001 From: Hari Sekhon Date: Tue, 10 May 2022 13:09:35 +0100 Subject: [PATCH] updated gcp_secrets_to_kubernetes.sh --- gcp_secrets_to_kubernetes.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcp_secrets_to_kubernetes.sh b/gcp_secrets_to_kubernetes.sh index 6a30054e..8c117b16 100755 --- a/gcp_secrets_to_kubernetes.sh +++ b/gcp_secrets_to_kubernetes.sh @@ -32,7 +32,7 @@ matches the current kubectl context's cluster and which do not have the label ku these must be combined using gcp_secrets_to_kubernetes_multipart.sh instead) For each secret, checks for a label called 'kubernetes-namespace', and if set, then creates the secret in that namespace, -otherwise loads to the current namespace. This can even be a comma separated list of namespace and will create the secret in each one +otherwise loads to the current namespace. This can even be a comma separated list of namespaces and will create the secret in each one Remember to execute this from the right GCP project configured to get the right secrets and with the right Kubernetes context selected to load to the right cluster