cert-manager-webhook-example/deploy/dnsimple/templates/production.cluster-issuer.yaml
Martin Parm 3142c584af Add support for using an existing token secret
- Add variable dnsimple.existingTokenSecret to the Helm chart
  to support using an existing secret. This is useful e.g. in
  combination with https://github.com/bitnami-labs/sealed-secrets.
- Add variable dnsimple.tokenSecretName to support configuring the
  name of the token secret.
2021-01-20 01:02:53 +01:00

27 lines
No EOL
899 B
YAML

{{- if .Values.clusterIssuer.production.enabled -}}
apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
name: {{ include "dnsimple-webhook.fullname" . }}-production
labels:
app: {{ include "dnsimple-webhook.name" . }}
chart: {{ include "dnsimple-webhook.chart" . }}
release: {{ .Release.Name }}
heritage: {{ .Release.Service }}
spec:
acme:
email: {{ .Values.clusterIssuer.email }}
privateKeySecretRef:
name: {{ include "dnsimple-webhook.fullname" . }}-production
server: https://acme-v02.api.letsencrypt.org/directory
solvers:
- dns01:
webhook:
config:
account: {{ .Values.dnsimple.account | quote }}
tokenSecretRef:
key: token
name: {{ include "dnsimple-webhook.tokenSecretName" . }}
groupName: {{ .Values.groupName }}
solverName: dnsimple
{{- end -}}