Description

When deploying Argo CD Image Updater v1.0.1, the pod becomes stuck in the Running phase but never becomes Ready.
The health probe continuously fails, and the controller never completes startup.

This occurs both:

• when restarting the Image Updater deployment, and
• when running more than 1 replica (leader election appears to stall).

Logs

time="2025-11-26T09:19:49Z" level=info msg="Controller runtime logger initialized." controller=imageupdater controllerGroup=argoproj.io
time="2025-11-26T09:19:49Z" level=info msg=starting app="argocd-image-updater: v1.0.1+cc39181"
time="2025-11-26T09:19:49Z" level=info msg="webhook server is disabled"
time="2025-11-26T09:19:49Z" level=info msg="starting manager"
I1126 09:19:49.918949       1 leaderelection.go:257] attempting to acquire leader lease argocd-image-updater-system/c21b75f2.argoproj.io...
time="2025-11-26T09:20:01Z" level=info msg="healthz check failed" statuses="[{}]"
time="2025-11-26T09:20:11Z" level=info msg="healthz check failed" statuses="[{}]"
...
(repeats indefinitely)

The pod stays running indefinitely with logs repeating:

healthz check failed: statuses="[{}]"

and the deployment never reaches a Ready state.

Expected Behavior

• Image Updater should start successfully
• Health check should return healthy
• Leader election should succeed even when running 2+ replicas

Actual Behavior

• Health check always fails
• Controller never becomes ready
• Leader election never completes
• Running more than 1 replica makes the issue even more consistent (every pod gets stuck)

Steps to Reproduce

1. Install Argo CD Image Updater v1.0.1 (Helm or manifests)
2. Restart the deployment
   OR
3. Scale replicas to 2+
4. Observe that the pods stay Running but never become Ready
5. Logs show repeated healthz check failed messages