Blogs > New To Kubernetes.....

Navigating the world of Kubernetes can feel overwhelming at first — with so many terms, resources, and configurations, it’s natural to have questions. This blog is your friendly guide to demystifying the basics, breaking down core concepts, and helping you get started with clarity and confidence. Let’s answer the questions you didn’t even know you had. 

What exactly is Kubernetes and why is it so popular?

Kubernetes is an open-source container orchestration platform designed to automate the deployment, scaling, and management of containerized applications. Originally developed by Google and now maintained by the CNCF (Cloud Native Computing Foundation), it allows teams to manage containers (like Docker) across clusters of machines seamlessly.

Scalability - Kubernetes makes it easy to scale applications up or down based on demand automatically.

High Availability & Fault Tolerance - It ensures apps remain available even when individual containers or nodes fail.

Automation - Automates deployment, rollouts, rollbacks, and self-healing (e.g., restarts crashed containers).

Portability - Works across different environments—on-prem, cloud, or hybrid—reducing vendor lock-in.

Community & Ecosystem - Backed by a huge open-source community and supported by major cloud providers (AWS, Azure, GCP).

Declarative Configuration - You define the desired state (e.g., 3 replicas), and Kubernetes works to maintain it continuously.

What are the core parts of a Kubernetes cluster?

Every Kubernetes cluster has two main parts:

• Control Plane

• Worker Nodes

These components work together to monitor, schedule, and maintain the state of your workloads across multiple servers, making Kubernetes scalable and resilient by design.

What is the Control Plane?

The Kubernetes Control Plane is the central management layer that maintains the desired state of the cluster. It ensures that applications are running as intended, scales resources as needed and makes key scheduling and orchestration decisions. When you interact with Kubernetes (e.g., using kubectl or applying a manifest), you're communicating with the control plane.

Core Components of the Kubernetes Control Plane:

1. kube-apiserver : The kube-apiserver is the central access point for all Kubernetes operations. It validates API requests and updates the cluster state through etcd. It also manages authentication, authorization, and admission controls to enforce security.

2. etcd : etcd is a distributed key-value store that holds all cluster data, including configurations and secrets. It ensures consistency using the Raft algorithm and is vital for restoring the cluster state during failures.

3. kube-scheduler : The kube-scheduler assigns unscheduled pods to the most appropriate nodes. It considers resource availability, affinity rules, and other constraints to optimize pod placement and maintain load balance.

4. kube-controller-manager : This component runs various controllers that reconcile the cluster’s current state with its desired state. It automates tasks like scaling, health checks, and replica management to keep the system stable.

5. cloud-controller-manager : Used in cloud environments, this component connects Kubernetes with cloud provider services like load balancers and volumes. It enables cloud-specific functionality without embedding it into the Kubernetes core.

What do Worker Nodes do?

In a Kubernetes cluster, worker nodes are the machines (VMs or physical servers) that run your actual applications in the form of containers. These nodes receive instructions from the control plane to launch, manage, and monitor workloads (pods).

Each worker node contains essential components like:

1. kubelet : talks to the control plane and ensures containers are running as instructed.

2. container runtime : like Docker or containerd, runs the actual containers.

3. kube-proxy : manages networking and enables communication between pods and services.

Worker nodes don’t make decisions, they just execute what the control plane tells them. Their job is to keep your apps running, healthy, and connected.

How Kubernetes runs the applications?

In Kubernetes, containers don’t run on their own, they are grouped inside Pods, which are the smallest deployable units in Kubernetes. A Pod can contain one or more containers that share the same network and storage.

These Pods are then scheduled to run on Worker Nodes, which are the machines (physical or virtual machines) in the cluster.

So the structure is simple: Containers → Pods → Nodes

Conclusion

Kubernetes has become the industry standard for container orchestration because it simplifies how we deploy, manage, and scale applications. By separating responsibilities between the Control Plane and Worker Nodes, it provides a powerful yet flexible framework that ensures high availability, automation, and portability across environments.

Whether you are managing microservices at scale or migrating to the cloud, understanding how Kubernetes works under the hood is the first step to unlocking its full potential.