go-control-plane VS kubernetes-ingress-controller

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.

Kong Ingress Controller for Kubernetes

Here you go! https://github.com/Kong/kubernetes-ingress-controller/issues/729

The key to handling modern dynamic, scalable workloads in Kubernetes is a networking stack that can deliver API management, a service mesh and an ingress controller. Kong Ingress Controller allows users to manage the routing rules that control external user access to the service in a Kubernetes cluster from the same platform.

For those organizations using Kubernetes for their container orchestration, Kong created the Kong Ingress Controller which implements authentication, transformations, and other functionalities (via plugins) across Kubernetes clusters. Kong Ingress Controller updates a standard Kubernetes implementation as shown below:

This article will walk through how easy it is to set up the open source Kong Ingress Controller as a Kubernetes API gateway on a cluster.

But here is the tricky part. There are lots of Ingress Controllers available. Some of them are opensource, but some of them are paid one. For this project I’ve chosen an “official” Kubernetes Ingress Controller based on Nginx. But please be not confused with another one, also based on Nginx but created by NGINX Inc - this one is paid. Apart from these both there are also other* Ingress Controller*s available like Kong Ingress, or Traefik.