Describe the bug
Although the argocd-operator pod log mentions the admin password as changed multiple times, the argocd-secret secret stayed untouched after modifications to the argocd-example-cluster secret were made. This led to the authentication failing...

Manually patching the argocd-secret with a bcrypt hash of the new password worked and I could log in.

To Reproduce

Following the docs: https://argocd-operator.readthedocs.io/en/latest/usage/basics/#secrets

Steps to reproduce the behavior:

1. Install argocd operator and create a new argocd instance.
2. Check the argocd-example-cluster and the argocd-secret secret
3. Patch the argocd-secret secret to contain a new password
4. Check the argocd operator pod logs and wait until nothing happens anymore
5. Try to log in using the new password
6. Authentication fails
7. The argocd-secret secret contents are still untouched and on the state before step 3.

Expected behavior
According to the documentation this should have worked and I should be able to log in.

Information

• Cluster TalosLinux with Kubernetes 1.30.1
• Operator installed using OLM
• argocd operator version v0.10.1 (the Catalogsource was taken from https://raw.githubusercontent.com/argoproj-labs/argocd-operator/v0.10.1/deploy/catalog_source.yaml

If there are more details you would like to know, feel free to reach out.

Kind Regards
Johannes