gateway-api
ingress
Our great sponsors
gateway-api | ingress | |
---|---|---|
29 | 7 | |
1,567 | 572 | |
6.0% | 3.7% | |
9.8 | 8.2 | |
6 days ago | 10 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.
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.
ingress
-
What are the most popular ingress controllers
Caddy
-
Nginx Modern Reference Architectures
That is true, unfortunately. We, the core maintainers, don't use k8s ourselves, so we need to defer to the community for help. See https://github.com/caddyserver/ingress
-
Show HN: Caddy v2.5.0
Caddy at its simplest form is an HTTP server. So you could use it to front end your application that otherwise isn't well suited for taking direct HTTP requests. Caddy would bring you other features like TLS support.
However I think in K8s world Caddy would make the most sense as an Ingress Controller. There is even a project as such: https://github.com/caddyserver/ingress
All traffic would terminate first at Caddy. Handling TLS, HTTP1/2/3, etc. Then passing it back to your application service/pod.
- Cloudflare Proxy Alternative
-
For local projects, do you change your node port range?
Sorry actually I'm mixing up caddy with traefik. And ingress is an http lb + something that talks to k8s to dynamically update the configuration. Caddy has a WIP ingress project https://github.com/caddyserver/ingress
-
Considering (and deciding against) a switch from Traefik to an Envoy-based Ingress Controller
We have an ingress controller in the works by the community here: https://github.com/caddyserver/ingress
What are some alternatives?
caddy-l4 - Layer 4 (TCP/UDP) app for Caddy
multus-cni - A CNI meta-plugin for multi-homed pods in Kubernetes
apisix-opa-plugin
aws-load-balancer-controller - A Kubernetes controller for Elastic Load Balancers
kubernetes-ingress-controller - :gorilla: Kong for Kubernetes: The official Ingress Controller for Kubernetes.
tyk-operator - Tyk Operator for Kubernetes
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
OPA (Open Policy Agent) - Open Policy Agent (OPA) is an open source, general-purpose policy engine.
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
nginx-proxy - Automated nginx proxy for Docker containers using docker-gen