multus-cni
gateway-api
multus-cni | gateway-api | |
---|---|---|
6 | 29 | |
2,195 | 1,572 | |
3.8% | 2.7% | |
8.0 | 9.8 | |
1 day ago | 3 days ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
multus-cni
-
Run a pod with static MAC address
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?
-
I could use some help figuring out which CNI to use
Multus CNI plug-in: https://github.com/k8snetworkplumbingwg/multus-cni
- Two different networks
-
K3s- v1.24
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.
-
Kubernetes with Kubeadm
Multus
-
Considering (and deciding against) a switch from Traefik to an Envoy-based Ingress Controller
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).
gateway-api
-
ArgoCD Deployment on RKE2 with Cilium Gateway API
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.
-
A Comprehensive Guide to API Gateways, Kubernetes Gateways, and Service Meshes
Kubernetes provides two APIs to achieve this, the Ingress API and the Gateway API.
-
Using k8s-apiserver as AAA server for microservices?
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.
-
load balancer and kubernetes
Maybe there's something in the new fangled gateways.
-
Service Mesh Considerations
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.
- EKS: is it possible to rewrite the URL with ALB?
-
Apache Apisix: Open-Source API Gateway and API Management Platform
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.
-
A quick glance at the Kubernetes Gateway API
-- https://gateway-api.sigs.k8s.io
-
Sharing load balancers between containers
While you're learning about ingresses, also look into the k8s Gateway API, which is the next generation. https://gateway-api.sigs.k8s.io/
-
Exposing k8s services
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.
What are some alternatives?
cilium - eBPF-based Networking, Security, and Observability
caddy-l4 - Layer 4 (TCP/UDP) app for Caddy
kilo - Kilo is a multi-cloud network overlay built on WireGuard and designed for Kubernetes (k8s + wg = kg)
apisix-opa-plugin
antrea - Kubernetes networking based on Open vSwitch
kubernetes-ingress-controller - :gorilla: Kong for Kubernetes: The official Ingress Controller for Kubernetes.
ingress - WIP Caddy 2 ingress controller for Kubernetes
tyk-operator - Tyk Operator for Kubernetes
kube-router - Kube-router, a turnkey solution for Kubernetes networking.
OPA (Open Policy Agent) - Open Policy Agent (OPA) is an open source, general-purpose policy engine.
kube-ovn - A Bridge between SDN and Cloud Native (Project under CNCF)
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols