![\"\"](\"https:\/\/cloudberry360.com\/blog\/wp-content\/uploads\/2025\/09\/container-restart-policy-1.jpg\")
<\/figure>\n<\/div>\n\n\nThis feature, a long-awaited enhancement, offers a range of practical applications. Let\u2019s explore its functionality and see how it can benefit us.<\/p>\n\n\n\n
The Limitations of a Single Restart Policy<\/strong>:<\/p>\n\n\n\n Before this feature, the restartPolicy was defined at the Pod level, so all containers shared the same policy (Always, OnFailure, or Never). This approach works for many cases but can be restrictive in others.<\/p>\n\n\n\n For instance, consider a Pod comprising a primary application container and an initialization container that performs initial setup. It may be desirable for the primary container to always restart upon failure, whereas the initialization container should execute only once and never restart. However, with a single Pod-level restart policy, this configuration was not feasible.<\/p>\n\n\n\n The Implementation of Per-Container Restart Policies<\/strong>:<\/p>\n\n\n\n With the introduction of the ContainerRestartRules feature gate, it is now possible to specify a restartPolicy for each container within a Pod\u2019s specification. Furthermore, restartPolicyRules can be defined to control restarts based on exit codes. This provides the necessary fine-grained control to manage complex scenarios effectively.<\/p>\n\n\n\n Use Cases: <\/strong><\/p>\n\n\n\n In-Place Restarts for Training Jobs:<\/strong><\/p>\n\n\n\n This feature can be particularly beneficial for training jobs, where in-place restarts may be required to ensure the completion of training processes.<\/p>\n\n\n\n In machine learning (ML) research, it is common to orchestrate a large number of long-running AI\/ML training workloads. In these scenarios, workload failures are inevitable. When a workload fails with a retriable exit code, it is desirable for the container to restart promptly without rescheduling the entire Pod, which incurs a substantial amount of time and resources. Restarting the failed container \u201cin-place\u201d is crucial for optimizing the utilization of compute resources. The container should only restart \u201cin-place\u201d if it failed due to a retriable error; otherwise, the container and Pod should terminate and potentially be rescheduled.<\/p>\n\n\n\n This functionality can now be achieved through container-level restartPolicyRules. The workload can exit with distinct codes to signify retriable and non-retriable errors. With restartPolicyRules, the workload can be restarted in-place swiftly, but only when the error is retriable.<\/p>\n\n\n\n Pods with Multiple Containers:<\/strong><\/p>\n\n\n\n For Pods that execute multiple containers, it may be necessary to establish different restart requirements for each container. Some containers may have a clear definition of success and should only be restarted upon failure. Others may require continuous restarts.<\/p>\n\n\n\n This capability is now feasible through a container-level restartPolicy, enabling individual containers to have distinct restart policies.<\/p>\n\n\n\n Example Configurations: <\/strong><\/p>\n\n\n\n 1. Restarting on specific exit codes: <\/strong><\/p>\n\n\n\n In this example, the container should restart if and only if it fails with a retriable error, represented by exit code 42.<\/p>\n\n\n\n To achieve this, the container has 2. A try-once init container: <\/strong><\/p>\n\n\n\n In this example, a Pod should always be restarted once the initialization succeeds. However, the initialization should only be tried once.<\/p>\n\n\n\n To achieve this, the Pod has an 3. Containers with different restart policies: <\/strong><\/p>\n\n\n\n In this example, there are two containers with different restart requirements. One should always be restarted, while the other should only be restarted on failure.<\/p>\n\n\n\n This is achieved by using a different container-level <\/p>\n","protected":false},"excerpt":{"rendered":" With the release of Kubernetes 1.34, a new alpha feature called Container Restart Policy and Rules has been introduced. This feature provides more precise control over container restarts within a Pod. It allows us to specify a restart policy for each container individually, overriding the Pod\u2019s global restart policy. Additionally, it enables conditional restarts of individual containers based on their exit codes. This feature is accessible through the ContainerRestartRules alpha feature gate. This feature, a long-awaited enhancement, offers a range…<\/p>\n","protected":false},"author":1,"featured_media":296,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17,16],"tags":[33,31],"class_list":["post-294","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops","category-kubernetes","tag-containerrestartpolicy","tag-kubernetes"],"acf":[],"_links":{"self":[{"href":"https:\/\/cloudberry360.com\/blog\/wp-json\/wp\/v2\/posts\/294","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cloudberry360.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cloudberry360.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cloudberry360.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cloudberry360.com\/blog\/wp-json\/wp\/v2\/comments?post=294"}],"version-history":[{"count":3,"href":"https:\/\/cloudberry360.com\/blog\/wp-json\/wp\/v2\/posts\/294\/revisions"}],"predecessor-version":[{"id":300,"href":"https:\/\/cloudberry360.com\/blog\/wp-json\/wp\/v2\/posts\/294\/revisions\/300"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cloudberry360.com\/blog\/wp-json\/wp\/v2\/media\/296"}],"wp:attachment":[{"href":"https:\/\/cloudberry360.com\/blog\/wp-json\/wp\/v2\/media?parent=294"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cloudberry360.com\/blog\/wp-json\/wp\/v2\/categories?post=294"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cloudberry360.com\/blog\/wp-json\/wp\/v2\/tags?post=294"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}restartPolicy: Never<\/code>, and a restart policy rule that tells Kubernetes to restart the container in-place if it exits with code 42.<\/p>\n\n\n\napiVersion<\/strong>: v1\nkind<\/strong>: Pod\nmetadata<\/strong>:\n name<\/strong>: restart-on-exit-codes\n annotations<\/strong>:\n kubernetes.io\/description<\/strong>: \"This Pod only restart the container only when it exits with code 42.\"\nspec<\/strong>:\n restartPolicy<\/strong>: Never\n containers<\/strong>:\n - name<\/strong>: restart-on-exit-codes\n image<\/strong>: docker.io\/library\/busybox:1.28\n command<\/strong>: ['sh', '-c', 'sleep 60 && exit 0']\n restartPolicy<\/strong>: Never # Container restart policy must be specified if rules are specified<\/em>\n restartPolicyRules<\/strong>: # Only restart the container if it exits with code 42<\/em>\n - action<\/strong>: Restart\n exitCodes<\/strong>:\n operator<\/strong>: In\n values<\/strong>: [42]<\/code><\/pre>\n\n\n\nAlways<\/code> restart policy. The init-once<\/code> init container will only try once. If it fails, the Pod will fail. This allows the Pod to fail if the initialization failed, but also keep running once the initialization succeeds.<\/p>\n\n\n\napiVersion<\/strong>: v1\nkind<\/strong>: Pod\nmetadata<\/strong>:\n name<\/strong>: fail-pod-if-init-fails\n annotations<\/strong>:\n kubernetes.io\/description<\/strong>: \"This Pod has an init container that runs only once. After initialization succeeds, the main container will always be restarted.\"\nspec<\/strong>:\n restartPolicy<\/strong>: Always\n initContainers<\/strong>:\n - name<\/strong>: init-once # This init container will only try once. If it fails, the Pod will fail.<\/em>\n image<\/strong>: docker.io\/library\/busybox:1.28\n command<\/strong>: ['sh', '-c', 'echo \"Failing initialization\" && sleep 10 && exit 1']\n restartPolicy<\/strong>: Never\n containers<\/strong>:\n - name<\/strong>: main-container # This container will always be restarted once initialization succeeds.<\/em>\n image<\/strong>: docker.io\/library\/busybox:1.28\n command<\/strong>: ['sh', '-c', 'sleep 1800 && exit 0']<\/code><\/pre>\n\n\n\nrestartPolicy<\/code> on each of the two containers.<\/p>\n\n\n\napiVersion<\/strong>: v1\nkind<\/strong>: Pod\nmetadata<\/strong>:\n name<\/strong>: on-failure-pod\n annotations<\/strong>:\n kubernetes.io\/description<\/strong>: \"This Pod has two containers with different restart policies.\"\nspec<\/strong>:\n containers<\/strong>:\n - name<\/strong>: restart-on-failure\n image<\/strong>: docker.io\/library\/busybox:1.28\n command<\/strong>: ['sh', '-c', 'echo \"Not restarting after success\" && sleep 10 && exit 0']\n restartPolicy<\/strong>: OnFailure\n - name<\/strong>: restart-always\n image<\/strong>: docker.io\/library\/busybox:1.28\n command<\/strong>: ['sh', '-c', 'echo \"Always restarting\" && sleep 1800 && exit 0']\n restartPolicy<\/strong>: Always<\/code><\/pre>\n\n\n\n