12. Kubernetes Services (ClusterIP, NodePort, LoadBalancer, ExternalName)

Video Overview

This note explains:

• Why Kubernetes Services are needed
• Problems with direct Pod communication
• Types of Services (VERY IMPORTANT)
• Real-world traffic flow

📌 Backbone of Kubernetes Networking

---

❌ Concept 1: Problem Without Services

Warning

Pods are NOT reliable for direct communication

---

🚫 Issues:

• 🔁 Pod IPs keep changing (ephemeral) :contentReference[oaicite:0]{index=0}
• ❌ No stable endpoint
• ⚖️ No load balancing
• 🌐 No external access

---

🧠 Example Problem:

• Frontend pod → Backend pod
• Needs hardcoded IP ❌
• Pod restarts → IP changes → broken communication

---

✅ Concept 2: What is a Kubernetes Service?

Important

Quote

Service = Stable IP + DNS + Load Balancer for Pods

---

🎯 What it Provides:

• 🌐 Stable IP
• 🔗 DNS name
• ⚖️ Load balancing
• 🔄 Service discovery

---

🔁 How It Works

Example

User → Service → Pod
Pod → Service → Pod

---

🧠 Key Idea:

• Pods are dynamic
• Services are stable

---

📦 Concept 3: Types of Kubernetes Services

Important

1. ClusterIP
2. NodePort
3. LoadBalancer
4. ExternalName

---

🟢 1. ClusterIP (DEFAULT)

Success

Internal communication inside cluster

---

🧠 Definition:

• Exposes service inside cluster only
• NOT accessible externally

---

🔗 Use Case:

• Frontend → Backend communication

---

📞 Analogy:

• Office extension number ☎️
• Internal calls only

---

⚙️ YAML Example

apiVersion: v1
kind: Service
 
metadata:
  name: backend-svc
 
spec:
  type: ClusterIP
 
  selector:
    app: backend
 
  ports:
    - protocol: TCP
      port: 9090
      targetPort: 5678

---

🧠 Flow:

Pod → DNS (CoreDNS) → Service IP → Pod

---

🔑 Key Points:

• Stable DNS: backend-svc
• Load balances across pods
• Uses selectors

---

🟡 2. NodePort

Important

Exposes service outside cluster

---

🧠 Definition:

• Opens a port on every node
• Range: 30000–32767

---

📞 Analogy:

• Building front desk ☎️

---

⚙️ YAML

type: NodePort
 
ports:
  - port: 80
    targetPort: 80
    nodePort: 31000

---

🌐 Access:

NodeIP:NodePort

---

🔁 Flow:

User → NodeIP:NodePort → ClusterIP → Pod

---

⚠️ Key Points:

• Built on top of ClusterIP
• Need node IPs
• Not ideal for production

---

🔵 3. LoadBalancer

Success

Production-ready external access (Cloud)

---

🧠 Definition:

• Creates external load balancer
• Provides public IP

---

📞 Analogy:

• Call center ☎️

---

🔁 Flow:

User → LoadBalancer → NodePort → ClusterIP → Pod

---

⚠️ Important:

• Works in cloud (AWS, Azure, GCP)
• Not available in local clusters (like kind)

---

🧠 Reality Check

Warning

Rarely used directly in production

---

Why?

• No advanced routing
• No host-based routing

👉 Instead use:

• Ingress Controller

---

🟣 4. ExternalName

Info

Connects to external services

---

🧠 Definition:

• Maps service → external DNS

---

⚙️ YAML

apiVersion: v1
kind: Service
 
metadata:
  name: db-svc
 
spec:
  type: ExternalName
  externalName: mydb.amazonaws.com

---

🔁 Flow:

Pod → Service → External DB

---

🧠 Use Case:

• Connect to:
  • RDS
  • External APIs
  • Third-party services

---

💡 Why use it?

Important

• Avoid hardcoding external URLs
• Easy to update endpoints
• Decouples configuration

---

🔥 Concept 4: Selectors & Endpoints

Important

---

🎯 Selector:

selector:
  app: backend

• Matches pods with label

---

📍 Endpoints:

• Actual pod IPs behind service

---

🧠 Key Idea:

Quote

Service → Selector → Pods

---

🧠 Concept 5: Ports Explained

Field	Meaning
port	Service port
targetPort	Container port
nodePort	External access port

---

🧠 Concept 6: DNS Resolution

Info

• Handled by CoreDNS
• Converts:

backend-svc → ClusterIP

---

🧠 Final Flow (IMPORTANT)

Example

Frontend Pod → backend-svc → Backend Pod

---

⚠️ Key Observations

Warning

• Pods are ephemeral
• Services are stable
• NodePort = dev/testing
• LoadBalancer = cloud
• ClusterIP = internal

---

🧠 Final Takeaways

Summary

• Service = stable networking layer
• Enables:
  • Communication
  • Load balancing
  • Service discovery
• Core for microservices

---

📌 One-Line Summary

Quote

Pods change → Services stay constant ☸️

---