Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- en:modul:m321_aws:topics:09 [2025/09/30 21:22] – dgaravaldi
+++ en:modul:m321_aws:topics:09 [2025/10/27 09:42] (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.
-  - **Restart Policy**: 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**)
       * **Liveness probe**: if it fails, kubelet will kill & restart the container (useful for recovering stuck processes).
@@ Zeile 36: / Zeile 36: @@
 In the latter case, it will check with the defined ''RestartPolicy'' to choose what to do.
-The default value for ''restartPolicy'' is Always, meaning if a container within the Pod fails, Kubernetes will always attempt...
+The default value for ''restartPolicy'' is ''Always'', meaning if a container within the Pod fails, Kubernetes will always attempt to restart the Pod.