>_ IzzyLab

Topic breakdown

Init containers are containers that run SEQUENTIALLY and to full completion BEFORE the main ones start: their job is preparation (wait for a dependency, download data, apply a migration). Each must complete successfully with a zero exit code, otherwise the pod restarts init again and won't let the main containers in. In the manifest they live in a separate list spec.initContainers, adjacent to spec.containers, not inside it. The main container stays untouched.

What's checked

  1. manifest is valid (kubeconform)
  2. initContainer init is present
  3. main container web
  4. init container uses the busybox image

What it looks like