Kubernetes Architecture Overview

Let’s take a simple company structure where we have a CEO, managers, and employees.

Typically, in a company, we have multiple Teams but for simplicity let’s take an example of one Team where we have one manager in this diagram.

• The CEO’s primary responsibility is managing and executing high-level company tasks and driving the company in the right direction.
• The manager manages multiple team members and each team member will different tasks each task can consist of one or more activities.
• Team members update about their status with the manager, whether started or work in progress.

So at a high level, Kubernetes works the same way.

So in place of the CEO, we have an Admin or developer operating the Kubernetes clusters.

• An admin will interact with the Kubernetes clusters.
• The Master node is also referred to as Control Plane.
• The primary task for the master node is to deploy pods and containers on the worker node and monitor pods, nodes, and implement changes that respond to events and more.
• Containerized applications are deployed on worker nodes and run.
• Here each worker node reports the status of the workload and node status to the master and continuously watches for the new work assignments.
• The container is wrapped into the Pods and each pod can have one or more containers.
• Generally, there will be only one container per pod but can have two or more containers.

Some at a high level, the Kubernetes cluster consists of a control plane, worker nodes, pods, and containers.

• When you deploy Kubernetes, you get a cluster, a cluster is a set of machines, called nodes.
• A cluster has at least one worker node and at least one master node
• There can be more than one master node in a cluster to provide a cluster with failover and high availability.
• It is an open-source system also known as K8s.
• It is used for automating deployment, scaling, and management of containerized applications.

Also, check

Kubernetes Tutorials