Container Orchestration Explained

Learn more about Kubernetes:
Check out the IBM Cloud Kubernetes Service:

Earn a badge with NEW free hands-on Kubernetes labs:

We’ve talked about containerization already (, and now Sai Vennam is going to take a step back and talk about why container orchestration is necessary in the first place.

Build on IBM Cloud for free:

Interested in more lightboarding videos on Kubernetes and containers? Check out our other work:

Kubernetes vs. Docker: It’s Not an Either/Or Question:
Kubernetes Explained:
Kubernetes Deployments: Get Started Fast:
What are Microservices?:
What is Knative?:
What is Istio?:

#ContainerOrchestration #Containers #Kubernetes


43 thoughts on “Container Orchestration Explained”
  1. The things that container orchestration will do:

    1. Deployment
    2. Scaling: schedule containers to the right worker node for the best resources utilization
    3. Networking: create load balancers for external and internal services communication
    4. Operations and Insight: automatically bring up instances of a services in failure; provide integration points for service mesh and logging

  2. Sai , you have a subtle tone in voice that settles gently on the ears and diffuses in like the smoke cloud from the incense sticks our moms use. The board is an excellent choice.

  3. Did anyone notice that he was writing backwards mirrored? This is how some folks used to write status on glass on a warship… amazing talent… oh and btw great explanation too

  4. At 1:43 minutes, you say that these containers have key things like apps, OS and dependencies. But, in a previous video you said that containers do not contain OS. So, what is the reason behind mentioning OS here?

  5. Great videos, thanks…
    I have question, how does it manage multiple DB replicas ? Will the Write operation performed to all the DB replica's ? Blocking reads during it ?…

  6. َAre those Nodes VMs ? Which means we have 4 VMs here (3 Worker Nodes and 1 Master Node) ?

  7. Wait so Kubernetes has to run on it's own server? Won't that increase your costs by, in this case, 33% if you now need a whole new vm?

  8. Greatly explained, to the point, thank you! I would suggest to put load balancing (instead of putting it under network), availability with self healing. I would say that Containers is something that all developers and ops engineers need to learn as the essential component in building and running cloud native applications. It also brings next level/generation of virtualisation in a platform and language independent way.

  9. Thank You IBM for everything.. from my first PC Aptiva to this tutorial present day. 🙂

  10. Man! I've always hated containers, but this video motivated me to learn more about containerization. Simple, straight to the point,,,,, 10 points 🙂

  11. Amazing and simplified way of explanation . Thanks a lot Sai. This video adds to my knowledge.

  12. Developers may see a "singular view of the world," as you say, but that is a good thing. Keep in mind that without applications (and developers), users have no reason to use an "orchestration" system in the first place. Without customers using APPLICATIONS, you don't have a business.

Leave a Reply

Your email address will not be published.

Captcha loading...