The k8s-controller-sidecar we are using as a stopgap until T386694: Replace k8s-controller-sidecars with built in Sidecar containers on k8s 1.31 does not ensure sidecars are completely started before launching the main container with its payload.
This causes unexpected failure modes where for instance mediawiki tries to reach out to a service through the tls-proxy sidecar but it is not started yet.
We should find a way to ensure proper functionality of at least the envoy tls-proxy before starting mediawiki payloads in mw-cron and mw-script