Kubernetes Basics: Container Orchestration at Scale

Kubernetes Basics: Container Orchestration at Scale

Kubernetes (K8s) orchestrates containers at scale. Docker containers app portability; Kubernetes automates deployment, scaling, networking. Run 1000 container replicas across 100 servers, handle failures, scale up/down automatically. Kubernetes abstracts infrastructure: deploy once, runs on any cloud (AWS, Google, Azure) or on-premises.

Kubernetes Architecture

Master (Control Plane): Manages cluster. Scheduler: assigns pods to nodes. API Server: receives commands. etcd: stores cluster state. Worker Nodes: run containers. Each node runs kubelet (agent) and kube-proxy (networking). Pod: smallest Kubernetes unit. Wraps container(s). Usually 1 container per pod but supports multiple. Deployment: manages pod replicas. Desired state: 3 replicas. Kubernetes ensures exactly 3 running. Node dies: K8s starts replacement pod on healthy node.

Pods

Pod wraps 1+ containers sharing network namespace (same IP). Containers in pod communicate via localhost:port. Example: Main app container, sidecar logging container. Both in one pod. Ephemeral: pods created and destroyed. Don't store state in pods (lost on deletion). StatefulSets for stateful applications. Requests/Limits: Pod needs 256MB memory, limited to 512MB. K8s ensures node has resources before scheduling pod. Prevention: pod doesn't starve, node doesn't overload.

Deployments

Declarative: Define desired state, K8s achieves it. YAML: kind: Deployment; metadata: { name: myapp }; spec: { replicas: 3, selector: { matchLabels: { app: myapp } }, template: { metadata: { labels: { app: myapp } }, spec: { containers: [ { name: myapp, image: myapp:1.0 } ] } } }. kubectl apply -f deployment.yaml: Submit to cluster. K8s creates 3 pods running myapp:1.0 image. RollingUpdate: Replace pods gradually. 1 pod update → traffic redirected to others → next pod update. Zero downtime deployments. Rollback: if new version buggy, rollback to previous version.

Services

Pod IP temporary. Service provides stable IP/DNS. Type: ClusterIP (internal only), NodePort (external via node port), LoadBalancer (external via load balancer). Example: Service myapp exposes port 80. Traffic to myapp:80 routed to any pod labeled app=myapp. Pod dies: K8s removes from service endpoints. Traffic redirected to remaining pods. ServiceName (myapp) resolves to service IP via DNS. Clients connect to myapp:80; K8s routes internally.

ConfigMaps and Secrets

Environment variables, config files externalized. ConfigMap: non-sensitive data. Database host, app settings. Secret: sensitive data. API keys, passwords. Created: kubectl create configmap myconfig --from-literal=DB_HOST=localhost. Used in Pod: volumeMounts read config, environment variables set from ConfigMap. Secrets stored encrypted in etcd. Still visible in pod; use RBAC to restrict access.

StatefulSets

Deployments for stateless apps (multiple identical replicas). StatefulSets for stateful apps (each replica unique). Example: Database cluster, each node has identity (db-0, db-1, db-2). Ordered startup/shutdown. PersistentVolumes: storage persists across pod restarts. Pod dies → new pod mounts same volume, data available. Headless service: DNS resolves to individual pod IPs. Cluster aware: each node communicates with others by identity.

Persistent Volumes

Pod storage ephemeral (pod dies, storage lost). PersistentVolume (PV): storage resource. Provisioned by admin or dynamically. Claim (PVC): request storage. Pod uses PVC to mount storage. Example: PVC requests 10GB. PV allocated 10GB storage on network (NFS, EBS). Pod mounts; storage persists across restarts. Reclaim policy: Delete (storage deleted on PVC deletion), Retain (storage kept), Recycle (erased, reused).

Namespaces

Isolate resources in same cluster. Create namespace: kubectl create namespace staging. Resources in namespace: pods, deployments, services isolated from other namespaces. Resources in default namespace unreachable from staging namespace without explicit networking. Multi-team clusters: team-a namespace, team-b namespace. RBAC policies per namespace. Cost allocation: track resource usage per namespace.

Ingress

Expose HTTP/HTTPS outside cluster. Ingress controller: reads Ingress rules, configures external load balancer. Example: Ingress rule: hostname api.example.com → service api; hostname web.example.com → service web. Traffic to api.example.com routed to api service. Automatic SSL certificates: cert-manager provisions Let's Encrypt certificates. Zero-downtime certificate renewal.

Horizontal Pod Autoscaling (HPA)

Automatically scale pod count based on metrics. Rule: if CPU > 80%, add pods. If CPU < 30%, remove pods. Min replicas: 2, Max: 10. HPA monitors metrics (Prometheus), adjusts replicas. Traffic spike: CPU rises → HPA adds pods → load distributed → CPU normalizes. Traffic drop: HPA removes pods → reduce cost. Defines max to prevent runaway scaling.

Cluster Architecture Example

3 master nodes (for HA). etcd replicated across masters. 10 worker nodes. Deployment: 3 replicas myapp:1.0. Pods distributed across nodes. Service myapp routes traffic. If node dies: pods on that node rescheduled to healthy nodes. Persistent storage: network storage accessible from all nodes. Horizontal autoscaling: if load spike, HPA adds replicas (up to max). If node lacks resources, pod in Pending state until resources available or cluster scaled.

kubectl Commands

kubectl apply -f deployment.yaml: Deploy. kubectl get pods: List pods. kubectl logs pod-name: View logs. kubectl describe pod pod-name: Details. kubectl exec -it pod-name bash: Shell into pod. kubectl port-forward pod-name 8080:8080: Access pod from localhost. kubectl scale deployment myapp --replicas=5: Scale to 5 replicas. kubectl rollout undo deployment/myapp: Rollback. Extensive CLI; most common documented in Kubernetes docs.

Production Considerations

Resource requests/limits: Prevent pod starvation. Liveness probes: restart unhealthy pods. Readiness probes: exclude unhealthy from traffic. Network policies: restrict pod-to-pod traffic. Pod security policies: enforce security standards. Backup: regularly backup etcd (cluster state). Monitoring: Prometheus + Grafana track cluster metrics. Logging: centralize logs (ELK). Updates: canary deployments test new versions on small traffic percentage.

Under the Hood: Kubernetes Basics: Container Orchestration at Scale

Here is what separates someone who merely USES technology from someone who UNDERSTANDS it: knowing what happens behind the screen. When you tap "Send" on a WhatsApp message, do you know what journey that message takes? When you search something on Google, do you know how it finds the answer among billions of web pages in less than a second? When UPI processes a payment, what makes sure the money goes to the right person?

Understanding Kubernetes Basics: Container Orchestration at Scale gives you the ability to answer these questions. More importantly, it gives you the foundation to BUILD things, not just use things other people built. India's tech industry employs over 5 million people, and companies like Infosys, TCS, Wipro, and thousands of startups are all built on the concepts we are about to explore.

This is not just theory for exams. This is how the real world works. Let us get into it.

Object-Oriented Programming: Modelling the Real World

OOP lets you model real-world entities as code "objects." Each object has properties (data) and methods (behaviour). Here is a practical example:

class BankAccount:
    """A simple bank account — like what SBI or HDFC uses internally"""

    def __init__(self, holder_name, initial_balance=0):
        self.holder = holder_name
        self.balance = initial_balance    # Private in practice
        self.transactions = []            # History log

    def deposit(self, amount):
        if amount <= 0:
            raise ValueError("Deposit must be positive")
        self.balance += amount
        self.transactions.append(f"+₹{amount}")
        return self.balance

    def withdraw(self, amount):
        if amount > self.balance:
            raise ValueError("Insufficient funds!")
        self.balance -= amount
        self.transactions.append(f"-₹{amount}")
        return self.balance

    def statement(self):
        print(f"
--- Account Statement: {self.holder} ---")
        for t in self.transactions:
            print(f"  {t}")
        print(f"  Balance: ₹{self.balance}")

# Usage
acc = BankAccount("Rahul Sharma", 5000)
acc.deposit(15000)      # Salary credited
acc.withdraw(2000)      # UPI payment to Swiggy
acc.withdraw(500)       # Metro card recharge
acc.statement()

This is encapsulation — bundling data and behaviour together. The user of BankAccount does not need to know HOW deposit works internally; they just call it. Inheritance lets you extend this: a SavingsAccount could inherit from BankAccount and add interest calculation. Polymorphism means different account types can respond to the same .withdraw() method differently (savings accounts might check minimum balance, current accounts might allow overdraft).

Real-World System Design: Swiggy's Architecture

When you order food on Swiggy, here is what happens behind the scenes in about 2 seconds: your location is geocoded (algorithms), nearby restaurants are queried from a spatial index (data structures), menu prices are pulled from a database (SQL), delivery time is estimated using ML models trained on historical data (AI), the order is placed in a distributed message queue (Kafka), a delivery partner is assigned using a matching algorithm (optimization), and real-time tracking begins using WebSocket connections (networking). EVERY concept in your CS curriculum is being used simultaneously to deliver your biryani.

How the Web Request Cycle Works

Every time you visit a website, a precise sequence of events occurs. Here is the flow:

    You (Browser)          DNS Server          Web Server
        |                      |                    |
        |---[1] bharath.ai --->|                    |
        |                      |                    |
        |<--[2] IP: 76.76.21.9|                    |
        |                      |                    |
        |---[3] GET /index.html ----------------->  |
        |                      |                    |
        |                      |    [4] Server finds file,
        |                      |        runs server code,
        |                      |        prepares response
        |                      |                    |
        |<---[5] HTTP 200 OK + HTML + CSS + JS --- |
        |                      |                    |
   [6] Browser parses HTML                          |
       Loads CSS (styling)                          |
       Executes JS (interactivity)                  |
       Renders final page                           |

Step 1-2 is DNS resolution — converting a human-readable domain name to a machine-readable IP address. Step 3 is the HTTP request. Step 4 is server-side processing (this is where frameworks like Node.js, Django, or Flask operate). Step 5 is the HTTP response. Step 6 is client-side rendering (this is where React, Angular, or Vue operate).

In a real-world scenario, this cycle also involves CDNs (Content Delivery Networks), load balancers, caching layers, and potentially microservices. Indian companies like Jio use this exact architecture to serve 400+ million subscribers.

Production Engineering: Kubernetes Basics: Container Orchestration at Scale at Scale

Understanding kubernetes basics: container orchestration at scale at an academic level is necessary but not sufficient. Let us examine how these concepts manifest in production environments where failure has real consequences.

Consider India's UPI system processing 10+ billion transactions monthly. The architecture must guarantee: atomicity (a transfer either completes fully or not at all — no half-transfers), consistency (balances always add up correctly across all banks), isolation (concurrent transactions on the same account do not interfere), and durability (once confirmed, a transaction survives any failure). These are the ACID properties, and violating any one of them in a payment system would cause financial chaos for millions of people.

At scale, you also face the thundering herd problem: what happens when a million users check their exam results at the same time? (CBSE result day, anyone?) Without rate limiting, connection pooling, caching, and graceful degradation, the system crashes. Good engineering means designing for the worst case while optimising for the common case. Companies like NPCI (the organisation behind UPI) invest heavily in load testing — simulating peak traffic to identify bottlenecks before they affect real users.

Monitoring and observability become critical at scale. You need metrics (how many requests per second? what is the 99th percentile latency?), logs (what happened when something went wrong?), and traces (how did a single request flow through 15 different microservices?). Tools like Prometheus, Grafana, ELK Stack, and Jaeger are standard in Indian tech companies. When Hotstar streams IPL to 50 million concurrent users, their engineering team watches these dashboards in real-time, ready to intervene if any metric goes anomalous.

The career implications are clear: engineers who understand both the theory (from chapters like this one) AND the practice (from building real systems) command the highest salaries and most interesting roles. India's top engineering talent earns ₹50-100+ LPA at companies like Google, Microsoft, and Goldman Sachs, or builds their own startups. The foundation starts here.

Key Vocabulary

Here are important terms from this chapter that you should know:

💡 Interview-Style Problem

Here is a problem that frequently appears in technical interviews at companies like Google, Amazon, and Flipkart: "Design a URL shortener like bit.ly. How would you generate unique short codes? How would you handle millions of redirects per second? What database would you use and why? How would you track click analytics?"

Think about: hash functions for generating short codes, read-heavy workload (99% redirects, 1% creates) suggesting caching, database choice (Redis for cache, PostgreSQL for persistence), and horizontal scaling with consistent hashing. Try sketching the system architecture on paper before looking up solutions. The ability to think through system design problems is the single most valuable skill for senior engineering roles.

Where This Takes You

The knowledge you have gained about kubernetes basics: container orchestration at scale is directly applicable to: competitive programming (Codeforces, CodeChef — India has the 2nd largest competitive programming community globally), open-source contribution (India is the 2nd largest contributor on GitHub), placement preparation (these concepts form 60% of technical interview questions), and building real products (every startup needs engineers who understand these fundamentals).

India's tech ecosystem offers incredible opportunities. Freshers at top companies earn ₹15-50 LPA; experienced engineers at FAANG companies in India earn ₹50-1 Cr+. But more importantly, the problems being solved in India — digital payments for 1.4 billion people, healthcare AI for rural areas, agricultural tech for 150 million farmers — are some of the most impactful engineering challenges in the world. The fundamentals you are building will be the tools you use to tackle them.

Crafted for Class 7–9 • Programming & Coding • Aligned with NEP 2020 & CBSE Curriculum