A Pod defines init container A, then init container B, then the app. Init B fails and keeps restarting. What happens to later startup?
Select an answer to reveal the explanation.
Short Explanation
Init containers are a single-file line at security: person B does not enter until person A clears, and the main guest waits behind both. If B fails the check, nobody further down the line proceeds.
Full Explanation
Init containers run sequentially. Each must complete successfully before the next init—or any application container—starts. A failing init keeps the Pod in an init-related state and prevents Ready. Failures are not skipped after one attempt in the sense of allowing the app to start; they block progress until success or the Pod is otherwise handled.