|
You are here |
ectobit.com | ||
| | | | |
xvnpw.github.io
|
|
| | | | | In my previous post about Apache APISIX I have found path traversal in uri-blocker plugin. In this text I will focus on yet another ingress controller which is Traefik. It has feature called forward auth. At the end I will mention HAProxy ingress controller. | |
| | | | |
blog.mariom.pl
|
|
| | | | | There is an easy way to use base-auth for securing ingress access in Traefik, but, well - its base auth. Its not that secure nor easy / nice to use in browsers, especially on mobile devices. So for long time, I was thinking how to integrate Traefik Ingress with an SSO (Single Sign-On) solution. Prerequisites You will need some kind of SSO provider. Im using Forgejo (a fork of Gitea). I didnt need anything fancy, and I already had Gitea working, which had the OAuth2 provider out of the box. | |
| | | | |
www.paulsblog.dev
|
|
| | | | | Use Traefik Ingress Controller as Proxy in Kubernetes (k8s) to provide load balancing, name-based virtual hosting, and SSL termination | |
| | | | |
nodogmablog.bryanhogan.net
|
|
| | | In my previous post I showed how to run a single instance of a Web API application in Kubernetes using Minikube. In this post, I will show you how to deploy the same application, but this time there will be 3 instances of the application, with a load balancer routing traffic to each of the instances. | ||