As other compagnies, we've added in our DNS a wildcard to match all subdomains (excepted www) to point to our staging server. Each developer could then push their GIT branch, and our CI/CD create the container in our Kubernetes with a new Ingress rules to support TLS for this subdomain/branch (of course, there is a .htpasswd for theses subdomains).
This works fine since many months, but since few weeks we receive a lots of attacks on our servers, so we've tried to move to another server to investigate, and we've been blocked to renew some of our production TLS certs.
Someone have tried to reach some random subdomain (may be to found services and find security holes), but when they do that, Traefik seems to request to Let's Encrypt a TLS cert even if there is not Ingress route that match! So, each time this reduce our rate limit
We are temporary removed our DNS wildcard, to stop the attack and permit us in few days to recreate our production TLS certs.
Do you known how to prevent this kind of problem ? May be Traefik could check if the route/ingress exists before requesting a TLS cert ?