4 ms·
Ingress in K8S is too complex. We need some sane defaults. It seems like there are more decisions to be made upfront then are really necessary. We are settin
by adamgordonbell 6y ago
Ingress in K8S is too complex. We need some sane defaults. It seems like there are more decisions to be made upfront then are really necessary.
We are setting up our cluster and we ended up going with Traefik and I just published an interview with our architect where he explained why he choose Traefik. Excuse the plug, but its here:
https://blog.earthly.dev/building-on-kubernetes-ingress/#kubernetes-ingest-strategies- https://blog.earthly.dev/building-on-kubernetes-ingress/#kub...
The short version is that he finds it easier to setup than Nginx. I think learning curves are an important metric that must be considered as well.
- etxm 6y agoI started using Traefik originally because it was easy to run outside of k8s. This allowed our front end devs to run it locally when they were running local api servers.
- agbell 6y agoyeah, I've seen a couple great articles about using it for local development. I haven't tried this myself, Traefik is new to me. Here is one potential setup https://www.codementor.io/@slavko/unobtrusive-local-development-with-traefik2-docker-and-letsencrypt-15qw1ypoi8 https://www.codementor.io/@slavko/unobtrusive-local-developm...
- zamora21 6y agoThe things I hate about k8s. * opinionated and promoting opinionated software * CNI thou shalt not NAT * Service mesh NAT * east-west -vs- north-south as an explicit design statement * cloud integration or it's no better than ryo with 'legacy' approaches implemented by competent SA/SE (this is the k8s design goal anyway: mirror what a competent SA could do.) * Go