Init containers play badly with startup probes

Marc Dequènes (Duck)requested to merge
init_container_no_probes into main

Probing HTTP by default, or any other port, does not make sense for a container whose goal is to setup things and not run long-standing services.

Despite OpenShift honoring the startup probe configuration the Kubernetes documentation says: init containers do not support lifecycle, livenessProbe, readinessProbe, or startupProbe whereas sidecar containers support all these probes to control their lifecycle. (see https://kubernetes.io/docs/concepts/workloads/pods/init-containers/#differences-from-sidecar-containers)

Merge request reports