Nginx Introduces Native Support for Acme Protocol

Re:Nginx Introduces Native Support for Acme Protocol by supriyo-biswas on Wednesday August 13, 2025 @01:55PM (#44891626)

Only if they'd get the K8s ingress out of the WIP phase; I can't wait to possibly get rid of the cert-manager and ingress shenanigans you get with others.

[ Parent | on HN ]

Re:Nginx Introduces Native Support for Acme Protocol by reactordev on Wednesday August 13, 2025 @02:01PM (#44891723)

Yup. I can’t wait for the day I can kill my caddy8s service.

The best thing about caddy is the fact you can reload config, add sites, routes, without ever having to shutdown. Writing a service to keep your orchestration platform and your ingress in sync is meh. K8s has the events, DNS service has the src mesh records, you just need a way to tell caddy to send it to your backend.

The feature should be done soon but they need to ensure it works across K8s flavors.

[ Parent | on HN ]

Re:Nginx Introduces Native Support for Acme Protocol by pushrax on Wednesday August 13, 2025 @03:34PM (#44892793)

just send sighup to nginx and it will reload all the config—there's very few settings that require a restart

[ Parent | on HN ]

Re:Nginx Introduces Native Support for Acme Protocol by reactordev on Wednesday August 13, 2025 @03:38PM (#44892852)

Sure, how, from the container? The host it’s on? Caddy exposes this as an api.

[ Parent | on HN ]

Re:Nginx Introduces Native Support for Acme Protocol by 01HNNWZ0MV43FF on Wednesday August 13, 2025 @02:27PM (#44892043)

I think you can that with Nginx too, but the SWAG wrapper discourages it for some reason

[ Parent | on HN ]

Re:Nginx Introduces Native Support for Acme Protocol by ilogik on Wednesday August 13, 2025 @06:08PM (#44894454)

Traefik seems to be ok for us

[ Parent | on HN ]