---
title: "Comment by CDN Edge Ops on \"Automating TLS for Envoy Gateway Using cert-manager and ACME HTTP-01 (with Let's Encrypt)\" | Hashnode"
description: "Solid path for moving TLS off Ingress-style controllers onto Gateway API with cert-manager. The failure mode I see most is a Certificate that looks Ready while"
url: "https://hashnode.com/posts/automating-tls-for-envoy-gateway-using-cert-manager-and-acme-http-01-with-lets-encrypt/693f4195176f1c17694c24f1/comment/6aebb94744bbf5baf912d00c"
---

[Discussion](https://hashnode.com/posts/automating-tls-for-envoy-gateway-using-cert-manager-and-acme-http-01-with-lets-encrypt/693f4195176f1c17694c24f1)

Comment [Automating TLS for Envoy Gateway Using cert-manager and ACME HTTP-01 (with Let's Encrypt)](https://hashnode.com/posts/automating-tls-for-envoy-gateway-using-cert-manager-and-acme-http-01-with-lets-encrypt/693f4195176f1c17694c24f1)

[CDN Edge Ops](https://hashnode.com/@cdnedgeops)

[Nov 4](https://hashnode.com/posts/automating-tls-for-envoy-gateway-using-cert-manager-and-acme-http-01-with-lets-encrypt/693f4195176f1c17694c24f1/comment/6aebb94744bbf5baf912d00c)

Solid path for moving TLS off Ingress-style controllers onto Gateway API with cert-manager. The failure mode I see most is a Certificate that looks Ready while the Gateway listener still serves the previous secret, or an ACME challenge that never reaches the solver because a catch-all route or wrong listener hostname swallowed the challenge path. Pin the Certificate secretName to the exact Gateway TLS certificateRef, confirm the challenge solver Service/route is reachable on port 80 for every name on the cert, and watch CertificateRequest / Order / Challenge objects before blaming DNS.

Operationally I treat renew as a three-step check: secret data notAfter advanced, Gateway status shows the listener attached with that secret, and a client handshake to the public name shows the new SAN and dates. If browsers still show old dates after a successful Order, the data plane is almost always bound to a different Secret or a cached listener config — restart or roll the gateway pods only after confirming the Secret bytes changed, not before. Short-lived test names plus a dry-run issuer save a lot of rate-limit pain when iterating on the challenge path.
