Init Container [glossary]deterministic

One or more initialization containers that must run to completion before any app containers run.

fundamentalstoragescheduling

One or more initialization [containers](#gloss:container) that must run to completion before any app containers run.

Initialization (init) containers are like regular app containers, with one difference: init containers must run to completion before any app containers can start. Init containers run in series: each init container must run to completion before the next init container begins.

Unlike [sidecar containers](#gloss:sidecar-container), init containers do not remain running after Pod startup.

For more information, read [init containers](/docs/concepts/workloads/pods/init-containers/).

Sources

reference/glossary/init-container.md · doc — “One or more initialization containers that must run to completion before any app containers run.”

Related (8)

references Resize CPU and Memory Resources assigned to Containers — init containers conf=1

references Pod Lifecycle — init containers conf=1

references Pods — init containers conf=1

references Adopting Sidecar Containers — init containers conf=1

references What Happens After A Node Restart — init container conf=1

prerequisite_of CustomResourceDefinition — ai-suggested prerequisite conf=0.7

prerequisite_of Admission Controller — ai-suggested prerequisite conf=0.7

prerequisite_of Cluster Operations — ai-suggested prerequisite conf=0.7

← all Docs