Traefik-v2-examples VS ingress-nginx

Theres also traefik guide but the contrast in complexity is apparent right away.

Traefik that I tried first is very powerful but there are few abstraction layers and bit of complexity that I felt like I had to re-learn it every time I was about to do a change. But it is very powerful in dynamic enviroments where one spins often enough more new containers.

My first reverse proxy was traefik, but it was just too complex, with too many abstraction layers for my use. I needed to re-learn it every time I went to make changes.

I tried traefik. As I was learning it, which was like a week or two of effort, I actually wrote a guide that somehow got 500 stars on github...

Theres also traefik, that people recommend, but IMO for home stuff it is too complex with too many abstractions. Caddy is literally just giving it port 80 and 443 and a single clean config file.

Traefik is actuall business aimed and powerful and probably worth learning if you would need to manage lot of containers and change stuff dynamically on the fly. But it is just so damn complicated and you kinda need to re-learn it every time you return to it. Here is guide for that one..

You can try look here

Here is a decent guide that gets you going.

Have you considered going caddy instead of traefik?

How to reverse proxy with traefik

# Add NGINX ingress using Helm eks.HelmChart( self, "NginxIngress", cluster=cluster, chart="ingress-nginx", repository="https://kubernetes.github.io/ingress-nginx", namespace="ingress-nginx", values=helm_values )

ingress-nginx

The second one is a combination of tools: External DNS, cert-manager, and NGINX ingress. Using these as a stack, you can quickly deploy an application, making it available through a DNS with a TLS without much effort via simple annotations. When I first discovered External DNS, I was amazed at its quality.

resource "helm_release" "icrelease" { name = "nginx-ingress" repository = "https://kubernetes.github.io/ingress-nginx" chart = "ingress-nginx" version = "4.9.1" namespace = kubernetes_namespace.icnamespace.metadata[0].name set { name = "controller.ingressClassResource.default" value = "true" } }

helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo update helm upgrade --install ingress-nginx ingress-nginx/ingress-nginx --namespace ingress-nginx --create-namespace -f custom/ghost/nginx.yaml

For example, if you chose Nginx Ingress, you will use some of its dozens of annotations that are not portable if you decide to switch to another Ingress implementation like Apache APISIX.

The controller is installed with helm upgrade --install ingress-nginx ingress-nginx --repo https://kubernetes.github.io/ingress-nginx --namespace ingress-nginx --create-namespace

helm repo add jetstack https://charts.jetstack.io helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo add rancher-latest https://releases.rancher.com/server-charts/latest helm repo update helm repo list

Everything in the YAML snippets below — except for ingress configuration — relates to configuring the NGINX ingress controller. This includes customizing the default configuration.