ClusterIP vs NodePort vs LoadBalancer
ClusterIP, (DEFAULT, type) Service, ko, sirf, cluster, ke, ANDAR, se, hi, ACCESSIBLE, banata hai — INTERNAL, microservice-to-microservice, COMMUNICATION, ke, liye, IDEAL. NodePort, HAR, node, ke, EK, SPECIFIC, PORT, (30000-32767, range) PAR, Service, ko, EXPOSE, karta hai — OUTSIDE, se, node, IP:PORT, se, ACCESS, ho, sakta hai.
LoadBalancer, type, CLOUD, PROVIDER, (AWS, GCP, Azure) se, EK, EXTERNAL, LOAD, BALANCER, PROVISION, karta hai, JO, INTERNET, TRAFFIC, ko, DIRECTLY, Service, tak, ROUTE, karta hai — PRODUCTION, mein, PUBLIC-FACING, applications, ke, liye, MOST, COMMON, hai.
# ClusterIP (default)
kubectl expose deployment nginx --port=80 --type=ClusterIP
# NodePort
kubectl expose deployment nginx --port=80 --type=NodePort
# LoadBalancer (cloud environments mein)
kubectl expose deployment nginx --port=80 --type=LoadBalancer- ClusterIP = internal-only, default type
- NodePort = har node ke specific port par expose (30000-32767)
- LoadBalancer = cloud provider se external load balancer, production ke liye common
"ExternalName" EK, CHOTHA, Service, type, hai, JO, Kubernetes, DNS, ko, EK, EXTERNAL, DNS, naam, ki, TARAF, POINT, karta hai (CNAME, record, ki, TARAH) — koi, PROXYING, NAHI, hoti, sirf, DNS, LEVEL, PAR, REDIRECT, hai.
apiVersion: v1
kind: Service
metadata:
name: external-db
spec:
type: ExternalName
externalName: db.example.comNodePort, ki, RANGE, (DEFAULT, 30000-32767) cluster, CONFIG, mein, CUSTOMIZE, ki, ja, sakti, hai — LEKIN, MOST, teams, NodePort, DIRECTLY, use, karne, ke, BAJAY, Ingress, YA, LoadBalancer, PREFER, karti, HAIN.