tyk-operator
haproxy-ingress
| tyk-operator | haproxy-ingress | |
|---|---|---|
| 4 | 6 | |
| 189 | 1,005 | |
| 1.1% | - | |
| 7.8 | 8.4 | |
| 5 days ago | 9 days ago | |
| Go | Go | |
| Mozilla Public 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.
tyk-operator
-
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.
haproxy-ingress
-
So you want to deploy mTLS
This was all running on Kubernetes, coupled with Google Cloud SQL for PostgreSQL and an HAProxy deployment managed by an ingress controller (jcmoraisjr/haproxy-ingress with a modified config file template). Branch or test deployments were a little different: the database was deployed on Kubernetes directly, to make it simple to deploy additional environments without spinning up resources outside of Kubernetes.
- no service with name ingress-controller/ingress-default-backend found
-
Back to basics: accessing Kubernetes pods
It's implementation-dependent and implementations offer different features, e.g., Nginx, Traefik, HAProxy, etc.
-
Kubernetes Ingress: Nginx Ingress Edition
HAProxy Ingress is an ingress controller for HAProxy.
- which ingress controller do you prefer
-
In a HA setup, why do I need a load balancer for the kube-apiserver if can just ssh the next kube-apiserver if one was down?
Which k8s-HAProxy do you use, this https://github.com/haproxytech/kubernetes-ingress or this https://github.com/jcmoraisjr/haproxy-ingress or voyager?
What are some alternatives?
apisix - The Cloud-Native API Gateway
ingress-nginx - Ingress-NGINX Controller for Kubernetes
envoy - Cloud-native high-performance edge/middle/service proxy
kubernetes-ingress - HAProxy Kubernetes Ingress Controller
gateway-api - Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.
kubernetes-ingress-controller - :gorilla: Kong for Kubernetes: The official Ingress Controller for Kubernetes.
argocd-operator - A Kubernetes operator for managing Argo CD clusters.
skipper - An HTTP router and reverse proxy for service composition, including use cases like Kubernetes Ingress
wireguard-operator - Painless deployment of wireguard on kubernetes
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
easegress - A Cloud Native traffic orchestration system
traefik - The Cloud Native Application Proxy [Moved to: https://github.com/traefik/traefik]