Does the timeout config on Argo CD App Rollout lead to misleading HealthChecks if resources have initContainers?

i’ve been wrestling with argo cd for a while. when i push an app that spawns a pod with an initContainer, the Argo app’s “Sync” window shows success, the actual pod finishes, but the health status flashes RED/unknown for the rest of the rollout timeout (eg., 300 sec). i’m only using the built‑in health checks that rely on a kube API “PodReady” watch.

no clear docs mention initContainers effect? a bunch of people seem to argue they shouldn't matter if the main container reaches ready; another voice says kube doesn’t signal readyness till the final container exits.

1. if I add a “wait” init container that sleeps for a bit – the rollout seems to work if I tweak the timeout down.
2. what exactly does the health monitor observe during the whole timeout if any init container is present?
3. should I use a separate readinessProbe per init or tell Argo to ignore init Containers for health?

anybody already solved this or got a way to hack the settings? i'm missing the documentation and see varying patterns.

gl on who can answer and keep the fire burning.