You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/concepts/workloads/pods/pod-lifecycle.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -150,7 +150,7 @@ the `Terminated` state.
150
150
Kubernetes manages container failures within Pods using a [`restartPolicy`](#restart-policy) defined in the Pod `spec`. This policy determines how Kubernetes reacts to containers exiting due to errors or other reasons, which falls in the following sequence:
151
151
152
152
1.**Initial crash**: Kubernetes attempts an immediate restart based on the Pod `restartPolicy`.
153
-
1.**Repeated crashes**: After the the initial crash Kubernetes applies an exponential
153
+
1.**Repeated crashes**: After the initial crash Kubernetes applies an exponential
154
154
backoff delay for subsequent restarts, described in [`restartPolicy`](#restart-policy).
155
155
This prevents rapid, repeated restart attempts from overloading the system.
156
156
1.**CrashLoopBackOff state**: This indicates that the backoff delay mechanism is currently
0 commit comments