en:modul:m321_aws:topics:09

Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen Revision Vorhergehende Überarbeitung
Nächste Überarbeitung		 Vorhergehende Überarbeitung
en:modul:m321_aws:topics:09 [2025/09/30 21:21] – [How Kubernetes "self-heals"] dgaravaldien:modul:m321_aws:topics:09 [2025/09/30 21:23] (aktuell) – dgaravaldi
Zeile 3: Zeile 3:
  
   - **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.   - **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** (so called **Probes**)   - **Health checks** (so called **Probes**)
       * **Liveness probe**: if it fails, kubelet will kill & restart the container (useful for recovering stuck processes).       * **Liveness probe**: if it fails, kubelet will kill & restart the container (useful for recovering stuck processes).
  • en/modul/m321_aws/topics/09.1759260103.txt.gz
  • Zuletzt geändert: 2025/09/30 21:21
  • von dgaravaldi