tyk-operator
Tyk Operator for Kubernetes (by TykTechnologies)
gateway-api
Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs. (by kubernetes-sigs)
| tyk-operator | gateway-api | |
|---|---|---|
| 4 | 29 | |
| 189 | 1,572 | |
| 1.1% | 2.7% | |
| 7.8 | 9.8 | |
| 5 days ago | 2 days ago | |
| Go | Go | |
| Mozilla Public License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
tyk-operator
Posts with mentions or reviews of tyk-operator.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-05-04.
-
Kubernetes Ingress: Nginx Ingress Edition
Tyk Operator extends Ingress with Custom Resources to bring API Management capabilities to Ingress. Tyk Operator works with the Open Source Tyk Gateway & Tyk Cloud control plane.
- API Gateway & JWT
- Publish, Discover, Test & Consume APIs with Tyk Operator for Kubernetes. Feedback / Comments welcome
-
Extending Ingress for API Management use-cases. An alternative to Annotations
Feel free to visit https://github.com/TykTechnologies/tyk-operator for more examples, including using Tyk as an Ingress to ISTIO, automagic TLS with LetsEncrypt and more.
gateway-api
Posts with mentions or reviews of gateway-api.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-02-19.
-
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?
When comparing tyk-operator and gateway-api you can also consider the following projects:
apisix - The Cloud-Native API Gateway
caddy-l4 - Layer 4 (TCP/UDP) app for Caddy
envoy - Cloud-native high-performance edge/middle/service proxy
apisix-opa-plugin
argocd-operator - A Kubernetes operator for managing Argo CD clusters.
kubernetes-ingress-controller - :gorilla: Kong for Kubernetes: The official Ingress Controller for Kubernetes.
haproxy-ingress - HAProxy Ingress
OPA (Open Policy Agent) - Open Policy Agent (OPA) is an open source, general-purpose policy engine.
wireguard-operator - Painless deployment of wireguard on kubernetes
multus-cni - A CNI meta-plugin for multi-homed pods in Kubernetes
easegress - A Cloud Native traffic orchestration system
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
tyk-operator vs apisix
gateway-api vs caddy-l4
tyk-operator vs envoy
gateway-api vs apisix-opa-plugin
tyk-operator vs argocd-operator
gateway-api vs kubernetes-ingress-controller
tyk-operator vs haproxy-ingress
gateway-api vs OPA (Open Policy Agent)
tyk-operator vs wireguard-operator
gateway-api vs multus-cni
tyk-operator vs easegress
gateway-api vs metallb