k8s-aws-terraform-cluster VS ingress-nginx

git clone https://github.com/garutilorenzo/k8s-aws-terraform-cluster cd k8s-aws-terraform-cluster/example/

This terraform module will deploy a high available Kubernetes (K8s) cluster on Amazon AWS, using mixed on-demand and spot instances. K8s is installed through kubeadm ad usesContainerd as CRI and Flannel as CNI. You can also install longhorn for the persistent storage and nginx ingress controller for the ingress rules. Please note, this is only an example on how to Deploy a Kubernetes cluster. For a production environment you should use EKS or ECS.

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: