Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
I ran this command:
I spin up a single-node k8s cluster with ingress and AWS Route53. The https works in the beginning but after several rounds of CI/CD/system reboots, it stops to work and try to dig around for the root cause of the problem. Here are my configurations:
It produced this output:
E0325 08:56:20.831639 1 controller.go:186] orders controller: Re-queuing item "default/iconverse-k8s.tls-1171866450" due to error processing: error creating new order: acme: urn:ietf:params:acme:error:rateLimited: Error creating new order :: too many certificates already issued for exact set of domains: iconverse-k8s.taiger.io: see https://letsencrypt.org/docs/rate-limits/
My web server is (include version): tomcat 9.0.16
The operating system my web server runs on is (include version): Ubuntu 18.04
My hosting provider, if applicable, is: AWS EKS
I can login to a root shell on my machine (yes or no, or I don’t know): yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): no
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):
I am deploying it to a single-node kubernetes cluster. The whole idea of using the certificate manager is for it to self-manage. It doesn’t make sense to manually run the certificate manager to get the ssl cert, tear it down and then hopefully not forgetting to run it to refresh the certificate again every now and then before the certificate expires. What do I miss?