haproxy-ingress
haproxy-ingressI0120
haproxy-ingress | haproxy-ingressI0120 | |
---|---|---|
6 | 1 | |
1,006 | - | |
- | - | |
8.4 | - | |
2 days ago | - | |
Go | ||
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.
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?
haproxy-ingressI0120
-
no service with name ingress-controller/ingress-default-backend found
I0120 11:55:17.347244 6 launch.go:151] Name: HAProxyRelease: v0.8Build: git-1351a73Repository: https://github.com/jcmoraisjr/haproxy-ingressI0120 11:55:17.347337 6 launch.go:154] Watching for ingress class: haproxyI0120 11:55:17.347664 6 launch.go:364] Creating API client for https://10.3.0.1:443I0120 11:55:17.391439 6 launch.go:376] Running in Kubernetes Cluster version v1.16 (v1.16.4) - git (clean) commit 224be7bdce5a9dd0c2fd0d46b83865648e2fe0ba - platform linux/amd64F0120 11:55:17.401773 6 launch.go:177] no service with name ingress-controller/ingress-default-backend found: services "ingress-default-backend" is forbidden: User "system:serviceaccount:ingress-controller:ingress-controller" cannot get resource "services" in API group "" in the namespace "ingress-controller": RBAC: clusterrole.rbac.authorization.k8s.io "ingress-controller" not found kubectl get svc -n ingress-controller
What are some alternatives?
ingress-nginx - Ingress-NGINX Controller for Kubernetes
kubernetes-ingress - HAProxy Kubernetes Ingress Controller
kubernetes-ingress-controller - :gorilla: Kong for Kubernetes: The official Ingress Controller for Kubernetes.
skipper - An HTTP router and reverse proxy for service composition, including use cases like Kubernetes Ingress
tyk-operator - Tyk Operator for Kubernetes
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
traefik - The Cloud Native Application Proxy [Moved to: https://github.com/traefik/traefik]
containerd - An open and reliable container runtime
kubernetes-ingress - NGINX and NGINX Plus Ingress Controllers for Kubernetes
ingress-bfe - BFE Ingress Controller for Kubernetes
easegress - A Cloud Native traffic orchestration system
ingress - Ingress-NGINX Controller for Kubernetes [Moved to: https://github.com/kubernetes/ingress-nginx]