Our great sponsors
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
gateway-api
Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.
-
One thing I will note is that in the end only one process can listen at a certain endpoint (let's say 80 or 443) at the end of the day without some other complexity, AFAIK there isn't an Multus-like project for Ingress Controllers... A 2 tier setup would work but that just feels like overkill (especially for me).
You say that buuuuut that feels like it's been changing recently. It looks like caddy wants to go wherever NGINX can. Really hoping you're not mholt and this isn't a doyouknowwhoiam situation.
Yeah the Ingress objects are also shifting a bit underneath as well with the new Gateway API stuff, so there's that complexity to take into account. I much preferred using Traefik with the built in Ingress annotations because now if I decide to use some other library that picks up on them they literally don't exist (they're all IngressRoutes now).
We have an ingress controller in the works by the community here: https://github.com/caddyserver/ingress