gateway-api VS go-control-plane

It has already been a couple of years since the Kubernetes Ingress was defined as a “frozen” feature while further development will be added to the Gateway API.

Kubernetes provides two APIs to achieve this, the Ingress API and the Gateway API.

With all that said, K8s is not really meant to function as an API gateway to arbitrary services. You should look into API gateways such as NGINX, Kong or others, service meshes as others have already pointed out, or have a look at the K8s Gateway API the SIG is currently working on. The last one is in the early stages of adoption, but it could provide you with a nice way to do an API Gateway right in K8s.

Maybe there's something in the new fangled gateways.

Keep an eye on the Gateway API GAMMA Initiative as it is currently evolving with the goal of streamlining how services meshes can implement the Gateway API and reduce some overlap.

The selling point for me was ability to configure it using Kubernetes CRD's and future support of the Gateway API (under development - <https://gateway-api.sigs.k8s.io/>).

Developers can version their API now within helm charts or even yaml templates held along the code in their repositories.

-- https://gateway-api.sigs.k8s.io

While you're learning about ingresses, also look into the k8s Gateway API, which is the next generation. https://gateway-api.sigs.k8s.io/

The GatewayAPI model is quite different from the LB/ingress model, in the cluster it consists of gateway and route objects. Once the gateway is created routes connecting gateways to services are added. If you need to change how requests are distributed, the routes are updated but the gateway remains so the address and other configuration remains consistent. Gateways can be shared by multiple routes. Take a look at https://gateway-api.sigs.k8s.io/ its a bit terse but you will get the picture.

We are going to experiment with what's at the core of these service meshes - Go control plane

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.

Package serves a domain. Do not split one domain into several packages: Go does not have nested namespaces, so this is a pain to use, sometimes it is just a nightmare – have an unluck to use this thing. Dunno how about the general code quality, but calling this library UI subpar is a pure understatement.