mzinc/configmapsecret-controller repository overview

⁠ConfigMapSecrets

⁠Problem

I have a config⁠ that contains a mixture of secret and non-secret data. For some reason⁠ I can't use environment variables to reference the secret data. I want to check my config into source control, keep my secret data secure, and keep my non-secret data easily readable and editable.

⁠Solution

Use a ConfigMapSecret⁠ which is safe to store in source control. It's like a ConfigMap that includes your non-secret data, but it can reference Secret variables, similar to how container⁠ args can reference env variables. The controller will expand and render it into a Secret in the same namespace, keeping it updated to reflect changes to the ConfigMapSecret or its referenced variables.

Use SealedSecrets⁠ to keep your referenced Secret data secure.