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.
Thanks for reading ❤
If you liked this post, share it with all of your programming buddies!
Follow us on Facebook | Twitter
☞ An illustrated guide to Kubernetes Networking
☞ How To Set Kubernetes Ingress Controller on AWS?
☞ An Introduction to the Kubernetes DNS Service
☞ Deploying a Laravel app in Kubernetes on Google Cloud
☞ Top 10 Basic Facts About Kubernetes That You Didn’t Know
#kubernetes #devops #docker #aws