Caddy Gateway
Caddy Gateway is a work-in-progress Kubernetes Gateway API implementation that uses Caddy as its web server.
What Caddy Gateway is
Caddy Gateway is a work-in-progress Kubernetes Gateway API implementation that uses Caddy as its web server. Its controller watches Gateway API resources, creates Caddy JSON configuration, and sends it to associated Caddy pods through Caddy’s Admin API, allowing dynamic changes without downtime. You must supply the Caddy instance, which can run as a Deployment or DaemonSet; 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 needs Gateway API v1.4.0 CRDs installed, with some optional experimental CRDs also supported. Kubernetes Ingress resources are not supported, and the project says support is not planned. Installation instructions assume an existing configured Kubernetes cluster with components such as networking and DNS. The project is free under the Apache License, Version 2.0, with release assets for Linux amd64 and arm64. It warns that an Admin API without TLS can expose programmed certificates and recommends strict NetworkPolicies to restrict access.
Good
- Updates Caddy configuration dynamically without downtime
- One controller can manage multiple Caddy deployments
- Supports a range of Gateway API resources
- Free under the Apache License, Version 2.0
- Linux amd64 and arm64 release assets are listed
Watch out
- Project describes itself as work in progress
- Requires Gateway API v1.4.0 CRDs
- Users must provide a Caddy instance
- Kubernetes Ingress resources are not supported
Who it suits
Caddy Gateway may suit Kubernetes operators already running a configured cluster who want to manage Caddy through Gateway API resources. It assumes users can provide and administer the Caddy deployment and required CRDs.
Verdict
Caddy Gateway is aimed at Kubernetes environments built around Gateway API rather than Ingress. Its requirements include supplying Caddy and protecting the Admin API with TLS and network restrictions.
The facts
Each one read from Caddy Gateway's own pages, with the date it was checked.
What it does
- Architecture
- The controller watches Gateway API resources, generates Caddy JSON configuration, and sends it to associated Caddy pods.checked 7 Oct 2026
- Bring your own Caddy
- The controller requires a Caddy instance, which can run as a Deployment or DaemonSet; users can provide their own deployment.checked 7 Oct 2026
- Compatibility requirement
- The project requires Gateway API v1.4.0 CRDs, with some optional experimental CRDs supported.checked 7 Oct 2026
- Deployment model
- The controller can manage multiple separate Caddy deployments, and users must provide their own Caddy instance.checked 7 Oct 2026
- Dynamic configuration
- The controller uses Caddy’s Admin API to program Caddy dynamically without downtime.checked 7 Oct 2026
- Gateway API requirement
- The project requires Gateway API v1.4.0 CRDs to be installed in the cluster.checked 7 Oct 2026
- Ingress limitation
- Kubernetes Ingress resources are not supported, and the README says support is not planned.checked 7 Oct 2026
- Intended users
- Installation instructions assume users already have a Kubernetes cluster configured with components such as networking and DNS.checked 7 Oct 2026
- License
- The project is licensed under the Apache License, Version 2.0.checked 7 Oct 2026
- Multiple deployments
- One controller deployment can manage multiple separate Caddy deployments.checked 7 Oct 2026
- Project status
- The project describes itself as work in progress.checked 7 Oct 2026
- Purpose
- Caddy Gateway is a Kubernetes Gateway API implementation that uses Caddy as its web server.checked 7 Oct 2026
- Release assets
- The releases page lists v0.1.0 assets for Linux amd64 and Linux arm64.checked 7 Oct 2026
- Release status
- The releases page marks v0.1.0 as the latest release and dates it May 30, 2024.checked 7 Oct 2026
- 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.checked 7 Oct 2026
- Supported resources
- The README lists GatewayClass, Gateway, ReferenceGrant, BackendLBPolicy, BackendTLSPolicy, HTTPRoute, GRPCRoute, TLSRoute, TCPRoute, and UDPRoute as supported resources.checked 7 Oct 2026
Alternatives to Caddy Gateway
- 1
ngrok
Free planWebAPILinuxmacOS7.8From $10 a month - 2
Higress
Free planOpen sourceWebAPILinuxmacOS7.7Free plan - 3
Traefik Proxy
Free planOpen sourceWebAPILinuxmacOS7.7Free plan - 4
agentgateway
Free planOpen sourceWebAPILinuxmacOS7.5Free plan - 5
Kusk Gateway
Free planOpen sourceWebAPILinuxmacOS7.5Free plan - 6
BFE Ingress Controller
Free planOpen sourceAPILinuxmacOSSelf-hosted7.2Free plan