Administrator account login failure and ingress issue

[leesp-1975]

Describe the bug

values.yaml

config:
secret:
argocdServerAdminPassword: test0000

When deployed as above using helm, admin.password: test0000 is normally displayed in the Secrets name argocd-secret.
However, when logging in with admin // test0000 it fails

Or

kubectl -n argocd get secret argocd-initial-admin-secret -o jsonpath="{.data.password}" | base64 -d
Error from server (NotFound): secrets "argocd-initial-admin-secret" not found

server:
ingress:
enabled: true
ingressClassName: "nginx"
hostname: test.example.com

helm template result -->

-->
If you actually run it, ingress is not created.

Related helm chart

argo-cd

Helm chart version

7.4.2

To Reproduce

See Describe the bug

Expected behavior

See Describe the bug

Screenshots

No response

Additional context

No response

[leesp-1975]

The phrase argocd-initial-admin-secret that appears after installation should be removed.

htpasswd -nbBC 10 "" password | tr -d ':\n' | sed 's/$2y/$2a/

kubectl -n argocd patch secret argocd-secret
-p '{"stringData": {
"admin.password": "values",
"admin.passwordMtime": "'$(date +%FT%T%Z)'"
}}'

I was able to log in after the patch.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.