Caddy IngressController Implementation

Help
1

The problem I’m having:
I’m researching Caddy as part of an ongoing team IngressController analysis. I really like Caddy’s capabilities, however it doesn’t seem like there is a proper implementation of it as an IC.
I found this opensource IC project which is based on Caddy, however it doesn’t seem to encompass all of the base features.
I have Openshift clusters on which I want to deploy the ICs, and the good part about the above project is it works quite well with Ingress objects, but I don’t think it allows configurations more complex than a simple upstream pool + TLS + URI routing.
I’m looking for PKI/API Key implementations, upstream health checks, LB methods, rate limiting, things like JWT/OIDC support and WAF would be a nice bonus.

Is anyone familiar with this project and can provide more information? Or any other IngressController options based on Caddy? We would even consider an enterprise product from Caddy.

Links to relevant resources:

2

Unfortunately the core Caddy team doesn’t have expertise on kubernetes and such, so we defer to the community to provide that stuff. GitHub - caddyserver/ingress: WIP Caddy 2 ingress controller for Kubernetes is the “official” offering which is community maintained. If there’s missing features, then efforts should be put towards improving that.

That said, I’m sure Matt would be able to work with you to find the right solution, as a sponsor Sponsor the Caddy Project

3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.