Every THING is Internet of Thing

Container Orchestration

 
  • Akhilesh Moghe
  • Jan 14, 2022

What are Containers?

  • Containers are an application-centric method to deliver high-performing, scalable applications on any infrastructure of your choice.
  • Containers are best suited to deliver microservices by providing portable, isolated virtual environments for applications to run without interference from other running applications.
  • Containers encapsulate microservices and their dependencies but do not run them directly. Containers run container images.
  • A container image bundles the application along with its runtime, libraries, and dependencies, and it represents the source of a container deployed to offer an isolated executable environment for the application.
  • Containers can be deployed from a specific image on many platforms, such as workstations, Virtual Machines, public cloud, etc.

Container Orchestration

  • Container runtimes like runC, containerd, or cri-o we can use those pre-packaged images, to create one or more containers. All of these runtimes are good at running containers on a single host.
  • Container orchestrators are tools which group systems together to form clusters where containers' deployment and management is automated at scale while meeting the requirements mentioned below:
    • Fault-tolerance
    • On-demand scalability
    • Optimal resource usage
    • Auto-discovery to automatically discover and communicate with each other
    • Accessibility from the outside world
    • Seamless updates/rollbacks without any downtime.
  • A few different container orchestration tools and services:

Need for Container Orchestration

  • Although we can manually maintain a couple of containers or write scripts to manage the lifecycle of dozens of containers, orchestrators make things much easier for operators especially when it comes to managing hundreds and thousands of containers running on a global infrastructure.
  • Most container orchestrators can:
    • Group hosts together while creating a cluster.
    • Schedule containers to run on hosts in the cluster based on resources availability.
    • Enable containers in a cluster to communicate with each other regardless of the host they are deployed to in the cluster.
    • Bind containers and storage resources.
    • Group sets of similar containers and bind them to load-balancing constructs to simplify access to containerized applications by creating a level of abstraction between the containers and the user.
    • Manage and optimize resource usage.
    • Allow for implementation of policies to secure access to applications running inside containers.

Container Orchestrator Deployments

Search