Operator Version: 1.4.1
ArgoCD Version: 2.2.2

When a deploymentconfig is scaled to 0 ArgoCD puts in it progressing state forever:
HEALTH DETAILS: replication controller is waiting for pods to run

But since it's scaled to 0 pods will never run... so it's stuck.

I have tried scaling to 1 and after it scaled to 1 the status changed to Healthy as expected.
Scaling back to 0 caused the resource to be stuck in progressing again.

It's affecting 4 of my projects which currently have a deploymentconfig with 0 replicas (I don't want to scale them at this point).

Expected behavior:
Resources such as DeploymentConfigs scaled to 0 should not wait for the replication controller to see running pods.
"replication controller is waiting for pods to run" is false since it's status in openshift is "openshift.io/deployment.phase: Complete" it  knows it shouldn't have any resulting pods.