ingress-gce
application-gateway-kubernetes-ingress
ingress-gce | application-gateway-kubernetes-ingress | |
---|---|---|
7 | 9 | |
1,253 | 663 | |
0.4% | 0.2% | |
9.0 | 6.0 | |
1 day ago | about 24 hours ago | |
Go | Go | |
Apache License 2.0 | MIT License |
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.
ingress-gce
-
Server Name Indication (SNI)
You would first need to ensure you have an Ingress controller running. There are several available, such as nginx, Traefik, or the one provided by a cloud provider like GKE's Ingress-GCE or AWS's ALB Ingress Controller.
-
What are the most popular ingress controllers
ingress-gce (Google Cloud only)
-
Ingress controller confusion
Yes. Google's ingress controller talks to the GCP API and spins up an HTTP LB for you. The AWS LB Controller handles provisioning ALB's for you. And ... I guess other clouds exist too but these are the ones I am familiar with.
-
GKE Ingress: How to configure IPv4 and IPv6 addresses
At the end of the blog entry where I posted about how to fix a 502 error returned by GKE Ingress, I described an issue regarding health check configuration that has been opened for over three years. The one I mentioned here to support multiple addresses it's been opened for over four years. I think GKE Ingress is a remarkable resource. It can help you quickly release an application using K8S and cloud-native features wrapped in abstracted manifests, but it seems a bit left aside in some aspects.
-
GKE Ingress: How to fix a 502 bad gateway error
There is a considerable debate on this very topic in the issue Ingress Healthcheck Configuration on kubernetes/ingress-gce repository. Looking through issues on GitHub is an excellent way to understand how an application or service is evolving. It's been more than three years, and it's not resolved yet.
-
InterSystems Kubernetes Operator Deep Dive: Part 2
Google supports its own ingress controller, GCE, which you can use in place of an nginx controller. However, it has some drawbacks, for instance, lack of rewrite rules support, at least at the moment of writing.
-
Which ingress-controller do you use?
That ALB Controller is for AWS specifically. For Google Cloud you can use https://github.com/kubernetes/ingress-gce
application-gateway-kubernetes-ingress
-
AKS ingress - internal LB + App Gateway vs. public LB + Ingress/Gateway API
Unfortunately in some cases it works poorly. For more insights, read this - https://github.com/Azure/application-gateway-kubernetes-ingress/issues/1124
-
What do you think about the AGIC?
My main concern is about zero-downtime deployments - https://github.com/Azure/application-gateway-kubernetes-ingress/blob/master/docs/how-tos/minimize-downtime-during-deployments.md
-
App Gateway cannot reach AKS Service?
However, you better read and understand some specific behaviors of AGIC which are caused by its architecture - https://github.com/Azure/application-gateway-kubernetes-ingress/blob/master/docs/how-tos/minimize-downtime-during-deployments.md & https://github.com/Azure/application-gateway-kubernetes-ingress/issues/1124
-
What are the most popular ingress controllers
application-gateway-kubernetes-ingress (Azure only)
-
creating resource "kubernetes_ingress" with Terraform
Probably something like this https://azure.github.io/application-gateway-kubernetes-ingress/
-
The Kubernetes Ingress Concept and Ingress Controller (Part 1)
AKS Application Gateway Ingress Controller is an ingress controller that configures the Azure Application Gateway.
-
Aks ingress controller- Nginx+ vs AGIC
AGIC has a lack of annotations that I find nginx+ offers like server snippets and custom headers. granted you can write re-write rules for AGIC with the help of the portal, it resets everything if one pod fails and this is a major showstopper for me. More info about the exact issue I'm talking about is in this issue. Apart from this, like the previous comments, the extra WAF rules and compliances offered makes AGIC a good choice if you don't have any extra header addition requirements like i do.
- Looking for objective feedback on AKS
-
Is there a "delta" post from Kubernetes to Azure Kubernetes (AKS)?
If you want Azure to manage ingress, you can use Azure application gateway and application gateway ingress controller (agic). However, if you want a public/private combination, fox example if you have 8 microservices out of which you want 6 to have private endpoint and 2 to have public endpoint over https, then it cannot be dones as agic only supports one ip per port. Also one agic can only use one application gateway (With auto management, meaning it automatically manages the listeners, https settings, backendpools, probes etc. on app gateway). If you it as shared gateway, then you need to manage application gateway manually (with az cli). Also, its github page has good how tos (https://github.com/Azure/application-gateway-kubernetes-ingress).
What are some alternatives?
ingress-merge - Merge Ingress Controller for Kubernetes
ingress-nginx - Ingress-NGINX Controller for Kubernetes
Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages 🚀
gke-managed-certs - Managed Certificates for Kubernetes clusters using GCLB
kubernetes-ingress-controller - :gorilla: Kong for Kubernetes: The official Ingress Controller for Kubernetes.
devtron - Tool integration platform for Kubernetes
aws-load-balancer-controller - A Kubernetes controller for Elastic Load Balancers
envoy - Cloud-native high-performance edge/middle/service proxy
traefik - The Cloud Native Application Proxy
skipper - An HTTP router and reverse proxy for service composition, including use cases like Kubernetes Ingress