James E. Blair 9afaed4d37 Add option to manage secrets outside of helm
So that a user can manage the nodepool config file (which is a secret)
outside of helm, add an option where the user can specify the name
of that secret as a value, and if it's set, helm will not write the
secret and will tell k8s to mount that secret as the nodepool config
instead.

Change-Id: Ifa1b5e81b6c7700faef82f3b18aab157d042e735
2020-01-10 14:50:01 -08:00

16 lines
369 B
YAML

---
{{ if not .Values.config.secret }}
apiVersion: v1
kind: Secret
metadata:
namespace: {{ .Release.Namespace }}
name: {{ include "nodepool.fullname" . }}
labels:
{{- include "nodepool.common.labels" . | indent 4 }}
stringData:
nodepool.yaml: |
{{ toYaml .Values.config | indent 4 }}
clouds.yaml: |
clouds:
{{ toYaml .Values.clouds | indent 6 }}
{{ end }}