Caddy Gateway
github.com
- Free plan
- Linux
- API
- Self-hosted
What Caddy Gateway is
Caddy Gateway is a free, work-in-progress Kubernetes Gateway API implementation that uses Caddy as its web server. Its controller watches Gateway API resources, generates Caddy JSON configuration, and sends it to associated Caddy pods through Caddy’s Admin API, allowing dynamic updates without downtime. You must provide a Caddy instance as a Deployment or DaemonSet, and one controller deployment can manage multiple separate Caddy deployments. Supported resources include GatewayClass, Gateway, ReferenceGrant, BackendLBPolicy, BackendTLSPolicy, HTTPRoute, GRPCRoute, TLSRoute, TCPRoute, and UDPRoute. The cluster requires Gateway API v1.4.0 CRDs, with some optional experimental CRDs supported. Kubernetes Ingress resources are not supported and support is not planned. Installation assumes an existing Kubernetes cluster with networking and DNS. The project is licensed under Apache License 2.0, with v0.1.0 Linux amd64 and arm64 assets. The README warns that an unencrypted Admin API can expose programmed certificates.
Who it suits
Caddy Gateway suits Kubernetes operators who already run a cluster and can supply Caddy deployments. It fits teams adopting Gateway API resources rather than Kubernetes Ingress.
Good to know, and what to watch
- Free Apache 2.0 project
- Dynamic updates without downtime
- Manages multiple Caddy deployments
- Supports HTTP, gRPC, TLS, TCP, and UDP routes
- Linux amd64 and arm64 assets
- Work in progress
- Requires your own Caddy instance
- Requires Gateway API v1.4.0 CRDs
- Kubernetes Ingress unsupported
The verdict
Caddy Gateway provides dynamic Caddy management through Kubernetes Gateway API resources. It requires existing cluster infrastructure, Caddy deployments, and careful Admin API security configuration.
What the maker publishes
- Architecture
- The controller watches Gateway API resources, generates Caddy JSON configuration, and sends it to associated Caddy pods. source
- Bring your own Caddy
- The controller requires a Caddy instance, which can run as a Deployment or DaemonSet; users can provide their own deployment. source
- Compatibility requirement
- The project requires Gateway API v1.4.0 CRDs, with some optional experimental CRDs supported. source
- Deployment model
- The controller can manage multiple separate Caddy deployments, and users must provide their own Caddy instance. source
- Dynamic configuration
- The controller uses Caddy’s Admin API to program Caddy dynamically without downtime. source
- Gateway API requirement
- The project requires Gateway API v1.4.0 CRDs to be installed in the cluster. source
- Ingress limitation
- Kubernetes Ingress resources are not supported, and the README says support is not planned. source
- Intended users
- Installation instructions assume users already have a Kubernetes cluster configured with components such as networking and DNS. source
- License
- The project is licensed under the Apache License, Version 2.0. source
- Multiple deployments
- One controller deployment can manage multiple separate Caddy deployments. source
- Project status
- The project describes itself as work in progress. source
- Purpose
- Caddy Gateway is a Kubernetes Gateway API implementation that uses Caddy as its web server. source
- Release assets
- The releases page lists v0.1.0 assets for Linux amd64 and Linux arm64. source
- Release status
- The releases page marks v0.1.0 as the latest release and dates it May 30, 2024. source
- Security guidance
- The README warns that without TLS on Caddy’s Admin API, programmed certificates may be sent insecurely, and recommends strict NetworkPolicies to restrict API access. source
- Supported resources
- The README lists GatewayClass, Gateway, ReferenceGrant, BackendLBPolicy, BackendTLSPolicy, HTTPRoute, GRPCRoute, TLSRoute, TCPRoute, and UDPRoute as supported resources. source
Checked against the maker's pages on 7 Oct 2026.