tellerops / helm-teller

Allows you to manage configuration and secrets from multiple provider while masking the secrets at the deployment

💻 Never leave your terminal for secrets
📟 Same workflows for all your environments

---

Helm-teller

Helm Teller Allows you to inject configuration and secrets from multiple providers into your chart while masking the secrets at the deployment.

Why should i use it?

• More secure while using --debug or --dry-run the secrets will not show in the STDOUT
• Simple to integrate
• Rich of supported plugins
• Pull configuration and secret from multiple providers in one place
• Manage configuration from development to production in the same way

Installation

$ helm plugin install https://github.com/SpectralOps/helm-teller

Quick Start with helm teller

• Create .teller.yaml file in your helm chart.

providers:
  # vault provider
  vault:
    env_sync:
      path: redis/config
  # Consul provider
  consul:
    env:
      loglevel:
        path: log-level
 

• Set teller fields in your helm chart

apiVersion: v1
kind: ConfigMap
metadata:
  name: test-config-map
data:
  redis-host: {{ .Values.teller.host }}
  redis-password: {{ .Values.teller.password }}
  loglevel: {{ .Values.teller.loglevel }}

• Run helm teller deploy helm teller [install/upgrade] {PLUGIN_FLAGS} -- {NATIVE_HELM_FLAGS}.

See working example here

Contributing

See the contributing directory for more developer documentation