91dab0f121
The old config was generating a separate nginx ingress instead of attaching the HTTP challenge URL to our existing ingress (gitea-ingress)
21 lines
773 B
YAML
21 lines
773 B
YAML
apiVersion: certmanager.k8s.io/v1alpha1
|
|
kind: ClusterIssuer
|
|
metadata:
|
|
name: letsencrypt-production
|
|
spec:
|
|
acme:
|
|
# You must replace this email address with your own.
|
|
# Let's Encrypt will use this to contact you about expiring
|
|
# certificates, and issues related to your account.
|
|
email: ops@kosmos.org
|
|
server: https://acme-v02.api.letsencrypt.org/directory
|
|
privateKeySecretRef:
|
|
# Secret resource used to store the account's private key.
|
|
name: letsencrypt-production-account-key
|
|
# Add a single challenge solver, HTTP01 using the gitea-ingress
|
|
# https://docs.cert-manager.io/en/latest/reference/api-docs/index.html#acmechallengesolverhttp01ingress-v1alpha1
|
|
solvers:
|
|
- http01:
|
|
ingress:
|
|
name: gitea-ingress
|