Story (Required)

As of today, we create the initial admin password via operator and store it in argocd-cluster secret. The argocd-server creates a initial password as and when required.

From upstream docs ,

The initial password for the admin account is auto-generated and stored as clear text in the field password in a secret named argocd-initial-admin-secret in your Argo CD installation namespace.
You should delete the argocd-initial-admin-secret from the Argo CD namespace once you changed the password. The secret serves no other purpose than to store the initially generated password in clear and can safely be deleted at any time. It will be re-created on demand by Argo CD if a new admin password must be re-generated. 

We should let argocd-server handle the management of the initial admin password instead of managing it via operator. 

Background (Required)

https://issues.redhat.com/browse/GITOPS-3581?focusedId=24205007&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-24205007 

Approach (Required)

Get rid of argocd-cluster secret and admin password generation code from operator. 

Note: Make this change in refactored code. 

Acceptance Criteria (Mandatory)

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met