gateway-api VS multus-cni

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.

I have to plan the migration of our software we are running on a single node with docker-compose to K8, and i'm kinda lost in the plugins and the basic settings. One of our MS has to use static MAC address in order to run fine, bcs it's using a certificate. Is it possible to run a pod with static MAC address, or do you suggest to use multus-cni or something like this?

Multus CNI plug-in: https://github.com/k8snetworkplumbingwg/multus-cni

I opened a PR to add support for CNI v1.0.0 to Multus (https://github.com/k8snetworkplumbingwg/multus-cni/pull/879) but it was closed in July because 4.0 was "pretty near". Of course now it's almost February and we haven't seen so much as an Alpha of 4.0 since October. Sure wish they'd get their act together.

Multus

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).