X'inhuma s-Services f'Kubernetes, u x'inhi d-differenza bejn ClusterIP, NodePort, u LoadBalancer?

Question

IT Interview Practice · Accepted Answer

**Service** jagħti identità ta' netwerk stabbli (IP virtwali u isem DNS) lil *sett ta' Pods* magħżula skont il-labels. Peress li l-Pods huma effimeri u jbiddlu l-IPs, is-Service huwa l-indirizz dejjiemi li jużaw il-clients, u jagħmel **load-balance** fost il-Pods b'saħħithom warajh.

## Għaliex jeżistu s-Services

```text
Pods come and go (new IP each time). Clients need a STABLE endpoint.
A Service:
  → selects Pods by label  (selector: app=web)
  → gets a fixed virtual IP + DNS name (web.default.svc.cluster.local)
  → load-balances requests across the matching, READY Pods
```

## It-tliet tipi ewlenin ta' Service

```text
ClusterIP    (default)  → reachable ONLY inside the cluster
                          for pod-to-pod / internal service communication
NodePort               → opens a port on EVERY node (30000-32767)
                          external traffic hits nodeIP:nodePort → Service → Pods
LoadBalancer           → provisions an external cloud load balancer
                          gives a public IP that routes to the Service
```

```text
       Internet
          │
   ┌──────┴───────┐
   │ LoadBalancer │  (cloud LB, public IP)   ← for public services
   └──────┬───────┘
          │
   ┌──────┴───────┐
   │  NodePort    │  (node:30080)            ← exposes on each node
   └──────┬───────┘
          │
   ┌──────┴───────┐
   │  ClusterIP   │  (10.96.x.x, internal)   ← the base building block
   └──────┬───────┘
       Pods (app=web)
LoadBalancer builds on NodePort, which builds on ClusterIP.
```

## ClusterIP (intern)

```yaml
apiVersion: v1
kind: Service
metadata:
  name: web
spec:
  type: ClusterIP          # default; jista' jitħalla barra
  selector:
    app: web               # jaqbel mal-Pods bil-label app=web
  ports:
    - port: 80             # port tas-Service
      targetPort: 8080     # port tal-container
```

Pods oħra jilħquh permezz tad-DNS: `http://web` (l-istess namespace) jew `http://web.default.svc.cluster.local`.

## NodePort u LoadBalancer

```yaml
# NodePort — kull node jisma' fuq nodePort u jgħaddi lis-Service
spec:
  type: NodePort
  selector: { app: web }
  ports:
    - port: 80
      targetPort: 8080
      nodePort: 30080      # fakultattiv; 30000-32767
---
# LoadBalancer — il-cloud jipprovdi LB estern b'IP pubbliku
spec:
  type: LoadBalancer
  selector: { app: web }
  ports:
    - port: 80
      targetPort: 8080
```

```bash
kubectl get svc            # ara t-tipi, cluster IPs u external IPs
kubectl get endpoints web  # l-IPs veri tal-Pods wara s-Service
```

## Għaliex huwa importanti

Is-Services huma kif jaħdem in-networking f'Kubernetes, għalhekk li tifhimhom u l-ġerarkija tat-tipi huwa għarfien essenzjali ta' kuljum. Peress li l-Pods huma effimeri u jieħdu IPs ġodda kull darba li jerġgħu jinħolqu, ma tistax tippunta l-clients direttament fuq l-IPs tal-Pods; **Service** isolvi dan billi jipprovdi **IP virtwali u isem DNS stabbli** quddiem sett ta' Pods magħżula skont il-label, u billi jagħmel **load-balance** tat-traffiku biss fost il-Pods li huma Ready. It-tliet tipi jiffurmaw progressjoni b'layers: **ClusterIP** (id-default) jagħti indirizz intern biss għall-komunikazzjoni pod-to-pod u service-to-service u huwa l-blokka bażika; **NodePort** jiftaħ port fiss fuq kull node biex it-traffiku estern jista' jilħaq is-Service; u **LoadBalancer** imur aktar billi jipprovdi load balancer estern fil-cloud b'IP pubbliku — kull tip jinbena fuq dak ta' taħtu. Li tkun taf liema tuża — ClusterIP għat-traffiku intern tal-microservices, NodePort għal aċċess estern bażiku jew setups on-prem, LoadBalancer biex tesponi endpoint pubbliku fuq cloud (u, fil-prattika, Ingress quddiem is-Services ClusterIP għar-routing ta' HTTP) — huwa ewlieni biex tiddisinja kif il-komponenti jitkellmu ma' xulxin u mad-dinja ta' barra. Peress li kważi kull workload reali jeħtieġ konnettività stabbli u load balancing, li tifhem is-Services u t-tipi tagħhom huwa għarfien fundamentali tan-networking ta' Kubernetes li jitfaċċa kostantement kemm fid-disinn kif ukoll fid-dibagging.

Għaliex jeżistu s-Services

It-tliet tipi ewlenin ta' Service

ClusterIP (intern)

NodePort u LoadBalancer

Għaliex huwa importanti

Mistoqsijiet relatati