Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

AWS Logo
Menu

Kubernetes Architecture components

Before delving into Kubernetes architecture, it’s essential to grasp the fundamentals of Docker.

kubernetesdocker-compose
Manikanta Suru
Published Feb 9, 2024
Comments
Docker:-
The Docker CLI interacts with the Docker Daemon.
The Docker Daemon manages containers through the Container Runtime.
Docker Swarm provides orchestration capabilities on top of Docker.
For easy understanding taking one master and one worker node

The worker node consists of three components:

- kubelet
- kube-proxy
- container runtime
kubelet It ensures that containers are running as expected on the node.kube-proxy It manages network connectivity for services within the cluster.Container runtime It runs and manages containers on the node.

The worker node consists of five components:

API Server
Scheduler
Controller Manager
etcd
ccm
API Server: It exposes the Kubernetes API to the external world.
Scheduler: It schedules pods or resources within Kubernetes.
Controller Manager: It manages various tasks to ensure the smooth operation of the cluster.
Etcd: All Kubernetes information is stored as objects and key-value pairs within etcd.
CCM (Cloud Controller Manager): CCM interacts with the cloud provider’s APIs to manage cloud-specific resources such as load balancers, volumes, and networking, abstracting cloud-specific functionality from the core Kubernetes codebase to make Kubernetes more cloud-agnostic.
In the above diagram:
  • The “Master Node” represents the control plane of the Kubernetes cluster, which includes components like API Server, Scheduler, Controller Manager, etcd, and others.
  • The “Worker Nodes” are where the actual application workloads run. They host pods and containers and are managed by the control plane.
  • The arrows represent communication between the master node and worker nodes, indicating that the master node manages and controls the worker nodes in the cluster
     
Comments

Comments

Log in to comment