From 347bd6a6eaa1499c07d8cdcff83ab4b8ac1af34c Mon Sep 17 00:00:00 2001 From: Tim Bannister Date: Fri, 24 May 2024 21:55:04 +0100 Subject: [PATCH] Tweak heading level MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Make “Container restart policy” fit within the topic of how Pods handle container problems; it belongs there. --- content/en/docs/concepts/workloads/pods/pod-lifecycle.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md index 5e7a5bfdbf..9ac411910c 100644 --- a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md +++ b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md @@ -196,8 +196,7 @@ To investigate the root cause of a `CrashLoopBackOff` issue, a user can: application code. Running this container image locally or in a development environment can help diagnose application specific issues. - -## Container restart policy {#restart-policy} +### Container restart policy {#restart-policy} The `spec` of a Pod has a `restartPolicy` field with possible values Always, OnFailure, and Never. The default value is Always.