X'inhuma l-liveness, readiness, u startup probes, u meta tuża kull waħda?

Question

IT Interview Practice · Accepted Answer

Il-probes iħallu l-kubelet jiċċekkja s-saħħa ta' container u jaġixxi fuq ir-riżultat. Hemm tlieta: **liveness** (huwa ħaj, jew għandu jerġa' jibda?), **readiness** (huwa lest biex jirċievi traffiku?), u **startup** (spiċċa jibbutja?). Kull waħda tweġibl mistoqsija differenti.

## It-tliet probes b'ħarsa waħda

```text
LIVENESS   → "Is the app stuck/deadlocked?"   FAIL → kubelet RESTARTS the container
READINESS  → "Can it serve traffic right now?" FAIL → Pod removed from Service endpoints
                                                       (NOT restarted)
STARTUP    → "Has the slow boot finished?"     runs FIRST; while it runs, liveness &
                                                readiness are held off
```

## Readiness vs liveness — id-distinzjoni ewlenija

```text
Readiness controls TRAFFIC:
  → a Pod that fails readiness is pulled OUT of the Service load-balancer,
    but keeps running (e.g. it's warming a cache or a dependency is down)
Liveness controls LIFE:
  → a Pod that fails liveness is KILLED and restarted (it's broken beyond recovery)
Using liveness where you meant readiness causes needless restart loops.
```

## Definizzjonijiet tal-probes

```yaml
spec:
  containers:
    - name: app
      image: myapp:1.0
      ports: [{ containerPort: 8080 }]

startupProbe:            # jagħti lil starter bil-mod ħin qabel jibdew l-oħrajn
        httpGet: { path: /healthz, port: 8080 }
        failureThreshold: 30   # 30 * 10s = sa 5 min biex jibda
        periodSeconds: 10

readinessProbe:          # ikkontrolla t-traffiku
        httpGet: { path: /ready, port: 8080 }
        initialDelaySeconds: 5
        periodSeconds: 10

livenessProbe:           # erġa' ibda jekk mhux b'saħħtu
        httpGet: { path: /healthz, port: 8080 }
        periodSeconds: 10
        failureThreshold: 3
```

## Mekkaniżmi tal-probes

```text
httpGet    → GET a path; 2xx/3xx = pass         (most common for web apps)
tcpSocket  → can we open a TCP connection?       (for non-HTTP services)
exec       → run a command; exit 0 = pass        (custom checks)
grpc       → native gRPC health check
Key knobs: initialDelaySeconds, periodSeconds, timeoutSeconds,
           failureThreshold, successThreshold.
```

## Għaliex jeżistu l-startup probes

```text
Slow-starting apps (JVM warmup, big migrations) used to force you to set a huge
initialDelaySeconds on liveness — which then made real crashes slow to detect.
The startupProbe fixes this: it protects the slow boot, and ONLY after it passes
do liveness/readiness begin with their normal (tight) timings.
```

```bash
kubectl describe pod app     # ara l-failures tal-probe u r-raġunijiet tar-restart fl-events
kubectl get pod app          # il-kolonna READY tirrifletti r-readiness; RESTARTS tirrifletti l-liveness
```

## Għaliex huwa importanti

Il-health probes huma kif Kubernetes iwassal is-self-healing u r-routing sikur tat-traffiku, għalhekk li tifhem it-tliet tipi u meta tuża kull waħda huwa għarfien essenzjali tal-affidabbiltà. Id-distinzjoni kruċjali — waħda li twaqqa' ħafna inġiniera — hija bejn **readiness** u **liveness**: ir-readiness tikkontrolla t-**traffiku** (Pod li jfalli jinġibed barra mil-load-balancer tas-Service imma jibqa' jaħdem, ideali meta qed jisħon jew dipendenza hija temporanjament barra), filwaqt li l-liveness tikkontrolla l-**ħajja** (Pod li jfalli jinqatel u jerġa' jibda, għal meta huwa deadlocked lil hinn mill-irkupru). Li tħawwad it-tnejn — tuża liveness probe fejn ridt readiness — jikkawża restart loops bla bżonn u outages, għalhekk li tkun taf liema mistoqsija tweġib kull probe huwa direttament prattiku. Il-**startup** probe isolvi uġigħ storiku reali: apps li jibbutjaw bil-mod darba ġiegħlu `initialDelaySeconds` enormi fuq il-liveness (li dewwem is-sejba ta' crashes ġenwini), filwaqt li startup probe jipproteġi t-tieqa tal-boot u jħalli l-liveness/readiness jaħdmu bi timings normali u ssikkati biss ladarba jirnexxi l-istartup. Li tifhem il-mekkaniżmi tal-probes (`httpGet`, `tcpSocket`, `exec`, `grpc`) u l-knobs tat-tuning (`initialDelaySeconds`, `periodSeconds`, `failureThreshold`, eċċ.) iħallik tikkonfigura l-health checking b'mod korrett minflok bit-tħawwid. Peress li l-probes jiddeterminaw direttament jekk l-utenti jilħqux Pods b'saħħithom u jekk Pods imkissra jirkuprawx awtomatikament, li tagħmilhom sew huwa fundamentali biex tħaddem workloads affidabbli u ta' livell ta' produzzjoni fuq Kubernetes.

It-tliet probes b'ħarsa waħda

Readiness vs liveness — id-distinzjoni ewlenija

Definizzjonijiet tal-probes

Mekkaniżmi tal-probes

Għaliex jeżistu l-startup probes

Għaliex huwa importanti

Mistoqsijiet relatati