Dex pods refuse connections on cluster power-up, preventing oauth login to ArgoCD

[mhjacks]

Describe the bug On cluster power-up (after power down), gitops dex pods can refuse connections, which prevents login to argocd

To Reproduce Steps to reproduce the behavior:

1. Use the "Login via OpenShift" feature on GitOps operator 1.3+ (viewed most recently with 1.3.2 on OCP 4.8.25)
2. Power down the cluster entirely
3. Power up the cluster
4. Attempt to access ArgoCD again. Most likely will be greeted with an error about dex refusing connection

Expected behavior oauth login succeeds and argocd login allowed

Additional context Deleting the gitops-dex pods is an effective workaround - the new pods accept connections and allow login.

[mhjacks]

Might be related to https://github.com/argoproj-labs/argocd-operator/issues/47

[iam-veeramalla]

This is fixed by adding probes to the Dex container in the upstream .

Should be part of GitOps v1.6