The Role of A Container Cluster Manager
A better approach for deploying containers in production
Deploying Containers on a Single Container Host
Almost all the container runtimes have been designed to run containers on a single container host. This is by design; containers share the host operating system kernel and features such as cgroups, namespaces, chroot, SELinux & seccomp, etc for providing the isolation and security. Therefore a given set of containers may need to run on a single container host. At the moment none of the container runtimes available today provide a mechanism for integrating multiple container hosts together for sharing the workload except by using a container cluster manager. Figure 1 illustrates how a software solution deployed on a set of VMs can be moved to a containerized environment using a single container host:
This deployment model is straightforward, easier to setup and simple to use. It would fit very well for setting up a development environment on developer machines. However when moving the software solution beyond the dev environment and deploying in QA, performance test, pre-production and production environments the following…