From the course: Kubernetes Essential Training: Application Development

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

The scheduler and influencing container placement

The scheduler and influencing container placement - Kubernetes Tutorial

From the course: Kubernetes Essential Training: Application Development

Start my 1-month free trial

The scheduler and influencing container placement

“

- [Instructor] One of the really powerful features of Kubernetes is that we can give it as many worker nodes as we like, and it will run our pods on one of them. We don't have to be involved in that decision, and we usually don't care about the outcome. But the default strategy is, well, run the pod wherever it fits. Sometimes we want to override this default behavior. For example, we might want two pods that talk to each other a lot to be in the same worker node, so that the communication between them is as fast as possible. We might want two pods that are part of the same service, to be as far apart from each other as possible on different nodes, ideally in different availability zones. This way, any node or network failure that affects one is less likely to affect the other, meaning that as a whole, the service will still stay up. So I'm going to walk you through the four options you can see in this table, which is for…

Contents