Please log in to watch this conference skillscast.
When you deploy an application in Kubernetes, your code ends up running on one or more worker nodes. A node may be a physical machine or VM such as AWS EC2 or Google Compute Engine and having several of them means you can run and scale your application across instances efficiently. When there is an incoming request, the cluster routes the traffic to one of the nodes using a network proxy. But what happens when network proxy crashes? Does the cluster still work? Can Kubernetes recover from the failure?
In this talk, you'll learn how the traffic is distributed within a Kubernetes cluster and what happens when the network proxy is misbehaving.
YOU MAY ALSO LIKE:
- Scaling Microservices with Message Queues, Spring Boot and Kubernetes (SkillsCast recorded in November 2018)
- Fast Track to Chaos Engineering with Russ Miles (in London on 6th - 8th November 2019)
- Introduction to Docker Fundamentals (in London on 26th - 27th November 2019)
- Scala eXchange London 2019 (in London on 12th - 13th December 2019)
- µCon London 2020 - The Conference on Microservices, DDD & Software Architecture (in London on 27th - 29th May 2020)
- Keynote by Konrad Kokosa: What’s New in .NET Core 3.0 and .NET 5.0 for Performance and Memory-Aware Folks? (in London on 29th October 2019)
- NewDay Career Hub Drop-in (in London on 21st November 2019)
- DevOps and Microservices Better Together (SkillsCast recorded in October 2019)
- Contain Your Excitement: The Kubernetes Ingress Controller (SkillsCast recorded in October 2019)
Kubernetes Chaos Engineering: Lessons Learned in Networking