---
title: "Discussion on \"Automating TLS for Envoy Gateway Using cert-manager and ACME HTTP-01 (with Let's Encrypt)\" | Hashnode"
description: "Discussion on \"Automating TLS for Envoy Gateway Using cert-manager and ACME HTTP-01 (with Let's Encrypt)\". With the recent annoncements regarding the Gateway APIs and the end of the Ingress Nginx maintenance, some aspects (historically managed by the Ingress Nginx) need to be re-adapted, we’ll shre one of those today: the TLS certificates management throu..."
url: "https://hashnode.com/posts/automating-tls-for-envoy-gateway-using-cert-manager-and-acme-http-01-with-lets-encrypt/693f4195176f1c17694c24f1"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Automating TLS for Envoy Gateway Using cert-manager and ACME HTTP-01 (with Let's Encrypt)](https://devops.dina.ch/automating-tls-for-envoy-gateway-using-cert-manager-and-acme-http-01-with-lets-encrypt?utm_source=hashnode&utm_medium=feed)

With the recent annoncements regarding the Gateway APIs and the end of the Ingress Nginx maintenance, some aspects (historically managed by the Ingress Nginx) need to be re-adapted, we’ll shre one of those today: the TLS certificates management throu...

Dec 14, 2025 · 4 min read · devops.dina.ch  
Read the article

-   [#letsencrypt](https://hashnode.com/tag/letsencrypt)
-   [#gateway-api](https://hashnode.com/tag/gateway-api)
-   [#ssl](https://hashnode.com/tag/ssl)
-   [#tls](https://hashnode.com/tag/tls)
-   [#k8s](https://hashnode.com/tag/k8s)

## Written by

[Christophe Perroud](https://hashnode.com/@christopheperroud)

@christopheperroud · Switzerland

  
[View profile](https://hashnode.com/@christopheperroud)

Cloud engineer

## Responses 1

Markdown supported · ⌘↵ to post

[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.
