-
kubernetes-ingress-controller
:gorilla: Kong for Kubernetes: The official Ingress Controller for Kubernetes.
-
gateway-api
Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.
-
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.
Here you go! https://github.com/Kong/kubernetes-ingress-controller/issues/729
They're all complicated. It's noteworthy that of all the native K8s API objects, Ingress is the only one that didn't come with its own controller. They specifically wanted other people to implement that functionality and the various implementations out there rapidly fragmented with the use of annotations and CRD's. Now we have the Gateway API (previously Service API) effort trying to implement something more robust than the Ingress API that captures all the various things these implementers want to provide controls for, but it's been underway since 2019.
Piggy backing on /u/ztherion: this is actually not as uncommon as you would think. The envoy folks at Lyft decided early on not to release their highly customized internal control plane when they released the proxy, so instead there is a reference implementation that does basic stuff which many people use as a starting point for their own control plane. This is exactly what Istio is built on, and in the Envoy slack the channel for chatting about building their own is pretty busy.
Related posts
-
Kubernetes releases ingress2gateway tool for upcoming GA of Gateway API
-
How to quickly block unwanted IP address when using ingress-nginx without the need of redeployment workloads?
-
Using Kong Ingress Controller with Spring Boot Services
-
Full Stack Kubernetes with Kong Ingress Controller
-
Using Kubernetes Ingress Controller as an API Gateway