Today, we’re excited to announce the early-access preview of Traefik Pilot, a new SaaS global control plane, to simplify the management of Traefik running in production.
External reverse proxy and load balancing software like Traefik offer networking features and control that Docker Swarm cannot provide on its own.
Maesh 1.3, the latest version of the simpler service mesh, is now even more reliable, flexible, and widely available.
When adopting microservices, Kubernetes alone may not be enough to handle more complex networking challenges that arise. This is the job of a service mesh.
Kubernetes is often used to manage external-facing applications, so the need for protecting applications from harmful external traffic is nearly universal.
In this post, I will share a migration strategy that helped me move to Traefik 2 with very little downtime, one service at a time, with an easy way to rollback.
The Ingress Object itself already has a long history with K8s. It is still considered beta, which is kinda surprising for something that has been so long present in K8s. But why is that? And when will that change?
How should developers implement access control, particularly authentication, within the context of k8s?