ingress
application-gateway-kubernetes-ingress
ingress | application-gateway-kubernetes-ingress | |
---|---|---|
3 | 9 | |
13,202 | 662 | |
- | 0.2% | |
9.7 | 6.0 | |
over 1 year ago | 9 days 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
-
Expose multiple backends with multiple IPs with Kubernetes Ingress resources
I exposed a service with a static IP and an Ingress through an nginx controller as one of the examples of the kubernetes/ingress repository. I have a second LoadBalancer service, that is not managed by any Ingress resource that is no longer properly exposed after the adding the new resources for the first service (I do not understand why this is the case).
-
How to set up kubernetes NGINX ingress in AWS and SSL termination
I've deployed ingress controller from https://github.com/kubernetes/ingress/tree/master/examples/aws/nginx
-
Ingress responding with 'default backend - 404' when using GKE
I have read and tried pretty much everything that I could find, including stuff from here and here and here, but maybe I'm just missing something... any ideas?
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?
multus-cni - A CNI meta-plugin for multi-homed pods in Kubernetes
ingress-nginx - Ingress-NGINX Controller for Kubernetes
kubernetes-ingress - NGINX and NGINX Plus Ingress Controllers for Kubernetes
Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages 🚀
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
kubernetes-ingress-controller - :gorilla: Kong for Kubernetes: The official Ingress Controller for Kubernetes.
aws-load-balancer-controller - A Kubernetes controller for Elastic Load Balancers
devtron - Tool integration platform for Kubernetes
ingress-gce - Ingress controller for Google Cloud
envoy - Cloud-native high-performance edge/middle/service proxy
kubectl-aliases - Programmatically generated handy kubectl aliases.
skipper - An HTTP router and reverse proxy for service composition, including use cases like Kubernetes Ingress