All woֿֿֿֿ\men are created equal.
But when it comes to applications, this is not the case :-)
K8s has the ability to run different types of applications on a set of different infrastructure types. This gives us better utilization of our infrastructure, but it also brings challenges related to the types of infrastructure required for a specific application, and the dependencies between the different applications.
Some applications require higher bandwidth, some need a newer generation CPU family, some need GPU, etc.
Applications can also have "location" restrictions such as: must have at least 1 replica in AZ, must not run with other applications on the same node, etc.
You’ve got the idea. Although K8s is a very powerful system that manages our application deployment/configuration/lifecycle, it’s OUR responsibility to “tell” K8s the constraints and limitations of our application, scheduling-wise.
In this session, we’ll cover the different scheduling techniques in K8s and their use-cases:
Dependent applications - applications that must have other applications on the same node
Conflicting applications - applications that must not share the same node with other specific applications
Applications that need specific instance types (e.g. instances with a high bandwidth network)
Availability Zone restrictions
K8s pod scheduling – deep dive
Full Talk (40 Minutes)
Food & Swag Sponsors
Learn more about each of our Event Sponsors.