OnePasswordItem health status is stuck with status progressing in ArgoCD 2.5.x

[horavamartin]

Your environment

Operator Version: 1.6.0

Connect Server Version: 1.5.7

Kubernetes Version: 1.24.8

ArgoCD: 2.5.6

What happened?

ArgoCD v2.5.6 expects the resource OnePasswordItem to have a health check. Without the health check is the resource stuck with health status Progressing with detail Waiting for controller to report status and app is never healthy.

What did you expect to happen?

Implement or configure health check so app in ArgoCD wont be stuck with status Progressing but will end with status Healthy.

Steps to reproduce

1. Create a secret in 1Password.
2. Create OnePasswordItem in kubernetes cluster
3. Check synchronization in ArgoCD

[tomjohnburton]

Are you sure you have updated to latest version of the CRD?

[Satyam1210]

I believe this was solved in 1.5.0, as per #118. However issue still persists in operator version 1.8.0.

[edif2008]

Hey folks! 👋

I'm sorry to hear that this is still an issue, even after the work done in #118.

Would you mind providing additional details in terms of how ArgoCD looks for the status? That would help the team narrow down the issue and do the necessary tweaks to the current Status property of the CRD so that it is properly used by ArgoCD.