Konubinix' opinionated web of thoughts

Init Containers

Fleeting

Init containers are exactly like regular containers, except:

Init containers always run to completion. Each init container must complete successfully before the next one starts.

Init containers run and complete their tasks before the main application container starts. Unlike sidecar containers, init containers are not continuously running alongside the main containers

— https://kubernetes.io/docs/concepts/workloads/pods/init-containers/ ([2025-03-20 Thu])

sidecar container

These containers are used to enhance or to extend the functionality of the primary app container by providing additional services, or functionality such as logging, monitoring, security, or data synchronization, without directly altering the primary application code.

— https://kubernetes.io/docs/concepts/workloads/pods/sidecar-containers/ ([2025-03-20 Thu])

init container is created with its restartPolicy set to Always

— https://kubernetes.io/docs/concepts/workloads/pods/sidecar-containers/ ([2025-03-20 Thu])

sidecar containers ignore the pod-level restartPolicy

— https://www.baeldung.com/ops/kubernetes-pod-lifecycle ([2025-03-20 Thu])

Notes pointant ici