Sample Header Ad - 728x90

Is there a specialized OS for container orchestration?

0 votes
1 answer
96 views
Containers are intended to solve the "it worked on my machine" problem. Thus, the blueprint of containers has two compatibility requirements: the OS and the architecture. We often see a container image like linux/amd64, windows/amd64, linux/aarch64, etc. But, as container orchestration joins the picture, we all agree that the worker node or master node shouldn't use an OS other than Linux—like Windows—due to the overhead they introduce. Moreover, why did we introduce Virtual Machine (VM) technology? Can't we just directly use a single physical machine as a node? I mean, isn't it redundant and needless overhead if VMs run inside a single large physical machine where the hypervisor is installed? Specifically, a bare-metal hypervisor where the hypervisor itself is treated as a specialized OS. I mean, when that physical machine goes down, all corresponding VMs would go down too, right? So, instead of a hypervisor of the bare-metal type, can we just replace it directly with a container orchestrator? Thus, the container orchestrator itself can be viewed as a master node or worker node (it's switchable). I mean, that physical machine can switch roles as a master or a worker.
Asked by Muhammad Ikhwan Perwira (319 rep)
Jul 8, 2025, 11:53 AM
Last activity: Jul 8, 2025, 01:51 PM