Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- en:modul:m321_aws:topics:09 [2025/09/30 18:09] – dgaravaldi
+++ en:modul:m321_aws:topics:09 [2025/09/30 21:23] (aktuell) – dgaravaldi
@@ Zeile 1: / Zeile 1: @@
-===== How Kubernetes "self-heals" — the pieces =====
+===== How Kubernetes "self-heals" =====
-Let's first have an overview over the possible pieces of 'self-healing' mechanism by K8s.
+Let's first have an overview over the pieces of 'self-healing' mechanism by K8s.
   - **Controllers** (Deployment → ReplicaSet → Pods): A Deployment declares the desired number of pod replicas. The ''ReplicaSet'' owned by that Deployment ensures that number is kept. If a pod is deleted or a pod’s container exits, the ''ReplicaSet'' (and controller manager) will create a replacement pod.
-  - restartPolicy: Container-level restarts are controlled by the Pod’s ''restartPolicy'' (for Deployments it’s Always by default). If the container process exits, **kubelet** will restart it according to that policy.
+  - **Restart Policy**: Container-level restarts are controlled by the Pod’s ''restartPolicy'' (for Deployments the value ''Always'' is set by default). If the container process exits, **kubelet** will restart it according to that policy.
-  - Health checks
+  - **Health checks** (so called **Probes**)
       * **Liveness probe**: if it fails, kubelet will kill & restart the container (useful for recovering stuck processes).
       * **Readiness probe**: controls whether a pod is considered "ready" and included in Services’ endpoints. During shutdown you should fail readiness, so the pod is removed from Service endpoints before termination.