Kubernetes is agile, flexible and scalable. It is also complex, with a multitude of moving parts on and underneath the surface. When things go wrong, as they always (eventually) do, understanding what caused the problem could be stressful and time-consuming.

But does it have to be? Join Mickael Alliel, DevOps engineer at Komodor, as he deep-dives into:

• The obvious (and not so obvious) challenges of using Kubernetes
• Ways to create a troubleshooting-friendly environment
• Five best practices to simplify K8s troubleshooting