Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

Caddy Ingress Controller review

Free#17 of 28 in Kubernetes Ingress Controllers

A free, self-hosted ingress controller with automatic HTTPS and Helm installation.

7.6/10Editor score
Caddy Ingress Controller7.6 Visit Caddy

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Caddy Ingress Controller is a self-hosted Kubernetes controller for routing traffic to cluster services through Caddy. It monitors Kubernetes Ingress resources and configures routing from those resources. The controller is aimed at teams that want a straightforward Ingress API deployment with automatic HTTPS, while retaining control over the Kubernetes environment and certificate configuration.

HTTPS is the standout capability. The controller can provision certificates automatically for managed hostnames, generate on-demand TLS certificates, or use certificates supplied through Kubernetes TLS secrets. This gives teams several certificate-management paths without changing the underlying deployment model. Installation is handled through a Helm chart, and the published requirements are Kubernetes 1.19 or newer and Helm 3 or newer. The chart creates Kubernetes resources including the controller deployment and service.

Caddy Ingress Controller also supports a configurable Kubernetes LoadBalancer service and enables metrics in the default chart configuration. Its focus is basic Kubernetes ingress rather than a broad traffic-management, security, or integration suite. The repository describes the controller as WIP, so teams should consider that status when evaluating it for production use. It fits organizations seeking an open-source, self-hosted controller with automatic HTTPS and standard Ingress resource monitoring. Teams needing verified advanced traffic management, security capabilities, or wider platform integrations should choose an alternative with those requirements clearly covered.

Caddy Ingress Controller pros and cons

  • Where it wins
    • Automatic and on-demand HTTPS certificate provisioning
    • Helm installation with configurable load-balancer settings
    • Open source with metrics enabled by default
  • Where it doesn't
    • Requires Kubernetes 1.19 or newer and Helm 3 or newer
    • The repository describes the controller as WIP
    • Self-hosted deployment requires Kubernetes administration

Caddy Ingress Controller fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update