Containers and Kubernetes have revolutionized software delivery. Releasing apps and services as stateless container images makes it easy to create and destroy container instances as demand requires.
Encryption for network security is a non-trivial matter, particularly in complex environments. Traefik and Let’s Encrypt can make the process of securing Kubernetes clusters simpler, speedier, and more resilient.
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.
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?
The great promise of Kubernetes is the ability to easily deploy and scale containerized applications. How Load Balancers work together with the Ingress Controllers in a Kubernetes architecture?
Kubernetes is the de facto standard for teams developing cloud-native applications. In this article, we’ll review one of the most critical aspects of Kubernetes networking: The Ingress Controller.