mirror of
https://github.com/cert-manager/webhook-example.git
synced 2025-07-02 14:55:49 +02:00
3142c584af
- 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.
49 lines
1.4 KiB
YAML
49 lines
1.4 KiB
YAML
# The GroupName here is used to identify your company or business unit that
|
|
# created this webhook.
|
|
# For example, this may be "acme.mycompany.com".
|
|
# This name will need to be referenced in each Issuer's `webhook` stanza to
|
|
# inform cert-manager of where to send ChallengePayload resources in order to
|
|
# solve the DNS01 challenge.
|
|
# This group name should be **unique**, hence using your own company's domain
|
|
# here is recommended.
|
|
groupName: acme.neoskop.de
|
|
certManager:
|
|
namespace: cert-manager
|
|
serviceAccountName: cert-manager
|
|
# logLevel: 3
|
|
dnsimple:
|
|
account: ""
|
|
token: ""
|
|
|
|
# existingTokenSecret: false
|
|
# tokenSecretName:
|
|
clusterIssuer:
|
|
email: name@example.com
|
|
staging:
|
|
create: false
|
|
production:
|
|
create: false
|
|
image:
|
|
repository: neoskop/cert-manager-webhook-dnsimple
|
|
tag: 0.0.5
|
|
pullPolicy: IfNotPresent
|
|
nameOverride: ""
|
|
fullnameOverride: ""
|
|
service:
|
|
type: ClusterIP
|
|
port: 443
|
|
resources: {}
|
|
# We usually recommend not to specify default resources and to leave this as a conscious
|
|
# choice for the user. This also increases chances charts run on environments with little
|
|
# resources, such as Minikube. If you do want to specify resources, uncomment the following
|
|
# lines, adjust them as necessary, and remove the curly braces after 'resources:'.
|
|
# limits:
|
|
# cpu: 100m
|
|
# memory: 128Mi
|
|
# requests:
|
|
# cpu: 100m
|
|
# memory: 128Mi
|
|
|
|
nodeSelector: {}
|
|
tolerations: []
|
|
affinity: {}
|