Scheduling containers with Kubernetes: Is it that different than other schedulers?
Kubernetes has emerged as one of the leading container orchestrators. Sebastien Goasguen explores its architecture and compares it with other orchestration/scheduling systems, outlining the similarities and explaining why Kubernetes API primitives make all the difference.
Talk Title | Scheduling containers with Kubernetes: Is it that different than other schedulers? |
Speakers | Sébastien Goasguen (TriggerMesh) |
Conference | O’Reilly Velocity Conference |
Conf Tag | Build Resilient Distributed Systems |
Location | San Jose, California |
Date | June 20-22, 2017 |
URL | Talk Page |
Slides | Talk Slides |
Video | |
Kubernetes has emerged as one of the leading container orchestrators. Sebastien Goasguen explores its architecture and compares it with other orchestration/scheduling systems, outlining the similarities and explaining why Kubernetes API primitives make all the difference. Sebastien walks you through Kubernetes, demonstrating how the head node is set up, how the worker nodes communicate with it, and how to deploy it in a high-availability setup. He then compares it with other scheduling/orchestration systems, such as Swarm, Mesos, virtual machines orchestrators, and other high-performance computing systems like Maui, PBS, and Condor, outlining the similarities at a high architectural level and explaining where age sets them apart. (For example, HPC systems tend not to expose a REST API, and Swarm leverages peer-to-peer systems concepts.) Sebastien concludes with a look at the Kubernetes API resources that make up the basic containerized application primitives and explains why the Kubernetes API design is the main differentiating factor.