liveBook · Manning

Agent orchestration

As explained in Podman in Action: Secure, rootless containers for Kubernetes, microservices, and more

A container orchestrator is a system that schedules and manages container workloads across one or more machines.

Container orchestration schedules and manages container workloads across multiple machines or nodes. Orchestrators communicate with container engines, which run containers locally; container runtimes configure Linux kernel isolation and launch the application. section 1.1

Use the boundaries between these roles to choose the right tool:

  • Use an orchestrator for multi-machine workloads; Kubernetes is the primary example, alongside Docker Swarm and Apache Mesos. section 1.1
  • Use Podman or Docker to develop, manage, and run containers on one host, in rootless or rootful mode. section 1.1 section 1.4
  • Use CRI-O or containerd as engines serving Kubernetes, rather than treating Podman as a multi-machine orchestrator. section 1.1 section 1.4
Figure 1.1 Different open source projects dealing with containers within the categories of orchestrators, engines, and runtimes.

Compare open-source projects by their role as orchestrators, container engines, or OCI runtimes. section 1.1

How Podman in Action: Secure, rootless containers for Kubernetes, microservices, and more covers it

How deep it goes
Distinguishes orchestrators, engines, and runtimes, but stops short of deployment procedures or scheduling internals.
Examples
Names Kubernetes, Docker Swarm, and Apache Mesos as orchestrators, with CRI-O and containerd serving Kubernetes.
What you can do after
Evaluate whether a workload needs a single-host container engine or a multi-machine orchestrator.
How it connects
Connects Kubernetes, Docker Swarm, Apache Mesos, container engines, and OCI container runtimes.

Also explained in

Compare how 11 books explain agent orchestration →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Podman in Action: Secure, rootless containers for Kubernetes, microservices, and more. The section links point to the parts of the book it draws on.