I’m spinning up a new service in Kubernetes using the kube-cert-manager tool. I made a developer mistake, where I accidentally set the tls domain name to be
foo.bar.com instead of
I use Google Cloud domains, and I did not have a cloud domain for
bar.com, but instead have
environment.bar.com. I created the deployment and got several errors that in turn rate-limited me:
kube-cert-manager-3589448969-qkxfx kube-cert-manager 2018/08/06 14:17:28 Error while processing certificate during sync: Error while obtaining certificate for new domain foo.bar.com: Error presenting token: No matching GoogleCloud domain found for domain bar.com.
when I fixed my mistake, I was already rate limited:
kube-cert-manager-3589448969-qkxfx kube-cert-manager 2018/08/06 15:01:45 Creating ACME client for googlecloud provider for foo.environment.bar.com kube-cert-manager-3589448969-qkxfx kube-cert-manager 2018/08/06 15:01:46 [INFO] acme: Registering account for firstname.lastname@example.org kube-cert-manager-3589448969-qkxfx kube-cert-manager 2018/08/06 15:01:46 Error while processing certificate during sync: Error while registering user for new domain foo.environment.bar.com: acme: Error 429 - urn:acme:error:rateLimited - Error creating new registration :: too many registrations for this IP: see https://letsencrypt.org/docs/rate-limits/
(stating the obvious: removed e-mails and domains for privacy)
Is there any way to undo the IP rate limit? I apologize for the mistake, this was for a dev environment and I assumed we had were using the staging let’s encrypt server but the dev environment was configured to also use the production server.