In the initial days, the worker node was called a “minion.” It is similar to you wanting to achieve or complete a project, and then wanting to divide the project into multiple modules with at least one manager managing and monitoring the progress. Kubernetes architecture works the same as there will be one or more master and zero or more worker nodes/nodes. The master node is the one that coordinates various activities and supervises the entire cluster of nodes. One or more nodes become master as well as slaves, respectively.

With the distributed system there comes the concept of master-slave. Kubernetes follows the distributed systems paradigm where a cluster (i.e., collection of nodes) appears to its users as one giant machine. The purpose of Kubernetes is to host your application, in the form of containers, in an automated fashion so that you can easily deploy, scale-in and scale-out (as required), and enable communications between different services inside your application. Real-world applications, tools, and architecture are complex in nature so, the goal of this blog post is to understand and learn it in an easy way. To learn about any tool or technology, you must start with learning about its terminology and architecture.

Kubernetes is a production-grade container orchestration that manages automated container deployment, scaling, and management. Let’s understand the Kubernetes architecture in an easy way…

What is kubernetes in simple terms