skipper
haproxy-ingress
Our great sponsors
| skipper | haproxy-ingress | |
|---|---|---|
| 4 | 6 | |
| 3,013 | 1,005 | |
| 0.7% | - | |
| 9.7 | 8.4 | |
| 5 days ago | 8 days ago | |
| Go | Go | |
| GNU General Public License v3.0 or later | 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.
skipper
-
Using spring boot for a gateway
So my advice is: Don‘t implement anything someone else already did better and have a look at Skipper: https://github.com/zalando/skipper
-
Validating Admission Requests in a Validating Admission Webhook
That's all! You can find a complete example of an Admit func from the Validating Admission Webhook in Skipper. I've also included an abridged version at the end of this blog post.
-
Making the ValidatingWebhook Testable
This series is based on my experience adding a ValidatingAdmissionWebhook to Skipper, modern HTTP proxy.
-
Parsing Admission Requests in a Validating Admission Webhook
You can find an abridged version of admission.Handler under "Reference". For a complete example of a validating admission webhook being used in production, checkout the validating admission webhook in Skipper, our HTTP reverse proxy.
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?
opera-proxy - Standalone client for proxies of Opera VPN
ingress-nginx - Ingress-NGINX Controller for Kubernetes
kube-httpcache - Varnish Reverse Proxy on Kubernetes
kubernetes-ingress - HAProxy Kubernetes Ingress Controller
application-gateway-kubernetes-ingress - This is an ingress controller that can be run on Azure Kubernetes Service (AKS) to allow an Azure Application Gateway to act as the ingress for an AKS cluster.
kubernetes-ingress-controller - :gorilla: Kong for Kubernetes: The official Ingress Controller for Kubernetes.
botkube - An app that helps you monitor your Kubernetes cluster, debug critical deployments & gives recommendations for standard practices
tyk-operator - Tyk Operator for Kubernetes
k8tz - Kubernetes admission controller and a CLI tool to inject timezones into Pods and CronJobs
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]