application-gateway-kubernetes-ingress VS ingress-nginx

Unfortunately in some cases it works poorly. For more insights, read this - https://github.com/Azure/application-gateway-kubernetes-ingress/issues/1124

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

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

application-gateway-kubernetes-ingress (Azure only)

Probably something like this https://azure.github.io/application-gateway-kubernetes-ingress/

AKS Application Gateway Ingress Controller is an ingress controller that configures the Azure Application Gateway.

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.

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).

helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx

[7] https://github.com/kubernetes/ingress-nginx "GitHub - kubernetes/ingress-nginx: Ingress NGINX Controller for Kubernetes"

I'm really missing HTTP/3 in ingress-nginx for Kubernetes. I guess most people use a CDN/Load Balancer in front of it. I didn't find a good general purpose alternative for ingress-nginx yet.

(https://github.com/kubernetes/ingress-nginx)

# Create directory structure `mkdir -p ./ingress-controller/nginx/manifests/` # Generate manifest using helm template `helm template ingress-nginx ingress-nginx \ --repo https://kubernetes.github.io/ingress-nginx \ --version ${CHART_VERSION} \ --namespace ingress-nginx \ > ./ingress-controller/nginx/manifests/nginx-ingress.${APP_VERSION}.yaml`

helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo update helm install nginx-ingress ingress-nginx/ingress-nginx --namespace ingress-nginx --create-namespace

In order to expose your applications, you'll need an Ingress Controller. This runs on every node in the cluster and listens on ports 80 and 443 (HTTP and HTTPS). I choose the Nginx Ingress Controller, which is easy to install on Microk8s:

helm repo add prometheus-community https://prometheus-community.github.io/helm-charts helm repo add grafana https://grafana.github.io/helm-charts helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo update

Official GitHub repository: https://github.com/kubernetes/ingress-nginx