How can I create a secret in two namespaces using Helm?

To create a Secret in two namespaces using Helm, you can leverage the power of Helm templates and iteration. Here's how you can accomplish this:

1. Define Your Secret in a Values File:

- Start by defining the Secret's data in your values.yaml file or a custom values file. This could look something like this:

secretData:
  mysecretkey: "mysecretvalue"


2. Specify Target Namespaces:

- Define the target namespaces where the Secret should be created. This could be in the same values.yaml or in a different config value, example:

namespaces:
  - "namespace-a"
  - "namespace-b"


3. Create the Secret Template:

- In your Helm chart's templates directory, create a template for the Secret, for example secret.yaml. The content must dynamically generate the Secret resource for each namespace specified.

4. Use the Loop in the Secret Template:

- Here's a template for your templates/secret.yaml file that iterates over the namespaces:

{{ range $.Values.namespaces }}
---
apiVersion: v1
kind: Secret
metadata:
  name: my-secret
  namespace: {{ . }}
type: Opaque
data:
  {{- range $key, $value := $.Values.secretData}}
    {{ $key }}: {{ $value | b64enc }}
  {{- end}}
{{ end }}

- The code above loops through the namespaces defined in the namespaces variable in values.yaml and creates one Secret resource for each namespace. It also takes the data from secretData and encodes it with base64.

5. Deploy your Chart:

- When you deploy your Helm chart using helm install my-release ./my-chart, or helm upgrade my-release ./my-chart, Helm will generate a Secret in every namespace specified in your values.yaml.

6. Considerations:

- Make sure that the service account or user that's running the helm operation has permissions to create a secret in multiple namespaces.

- If you need to manage updates for these secrets, consider using a helm hook, or create a job to perform updates after chart install/upgrade.

- This method keeps all configurations in one place, while still respecting the separation of namespaces. It avoids duplication of configurations and facilitates efficient secret management across multiple environments.

Learn more about this