Add Let's Encrypt RFC2136/TSIG ClusterIssuers #327
Reference in New Issue
Block a user
Delete Branch "benvin/letsencrypt-clouddns-issuer"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Publicly-trusted wildcard certs via Let's Encrypt DNS-01, solved over RFC2136/TSIG against our own BIND. A one-time CNAME self-delegates
_acme-challenge.unkin.netinto theacme.unkin.netzone served by bind-external; cert-manager writes the challenge TXT there. No GCP/clouddns and no Vault secret involved. The existingvault-issuer(internal PKI) is untouched.letsencrypt(prod) andletsencrypt-staging, both using a dns01 rfc2136 solver: nameserver198.18.199.53:53, keycertmanager, HMACSHA256,tsigSecretSecretRef-> reflected Secretcertmanager-tsigkeysecret.cert-manager.io ClusterIssuerin the platform AppProject.Depends on #329 (bind-external: the acme.unkin.net zone, the certmanager TSIG key reflected into cert-manager, and the 198.18.199.53 nameserver) and on the one-time Google Cloud DNS delegation + NAT of the public IP :53 to 198.18.199.53. Earlier clouddns/Vault commits on this branch are reverted.
Add Let's Encrypt DNS-01 clouddns ClusterIssuersto Add Let's Encrypt RFC2136/TSIG ClusterIssuers