docs: Remove the username and password requirement from Argo CD Agent solution (#894)
Some checks failed
Scorecard supply-chain security / Scorecard analysis (push) Failing after 1m23s
Close stale issues and PRs / stale (push) Successful in 45s

Signed-off-by: Mike Ng <ming@redhat.com>
This commit is contained in:
Mike Ng
2025-03-17 10:44:57 -04:00
committed by GitHub
parent 0ced43d053
commit c88191f99e

View File

@@ -150,6 +150,7 @@ Run the following `helm` command:
```shell
helm -n argocd install argocd-agent-addon charts/argocd-agent-addon \
--set-file agent.secrets.cacrt=/tmp/ca.crt \
--set-file agent.secrets.cakey=/tmp/ca.key \
--set-file agent.secrets.tlscrt=/tmp/tls.crt \
--set-file agent.secrets.tlskey=/tmp/tls.key \
--set-file agent.secrets.jwtkey=/tmp/jwt.key \
@@ -197,28 +198,6 @@ argocd-agent-principal LoadBalancer 10.96.149.226 172.18.255.201 443:321
3. For details on operational modes and guidance on selecting the appropriate `agent.mode` (e.g., `managed` or `autonomous`),
refer to the [Argo CD Agent website](https://argocd-agent.readthedocs.io/latest/concepts/agent-modes/).
**Important:**
The default Argo CD Agent authentication scheme requires a principal user credentials store on the hub cluster
and corresponding agent authentication credentials (username and password) on the spoke/managed/workload clusters.
By default, the user store includes credentials for users `cluster1` through `cluster10`.
If your OCM managed cluster name is not in this range or if you want to customize your password,
you need to modify the following secrets:
```shell
# kubectl config use-context <hub-cluster>
kubectl -n open-cluster-management-hub edit secret argocd-agent-principal-userpass
```
```shell
# kubectl config use-context <managed-cluster>
kubectl -n argocd edit secret argocd-agent-agent-userpass
```
See [gen-creds.sh](https://github.com/argoproj-labs/argocd-agent/blob/main/hack/demo-env/gen-creds.sh)
for an example of how to create user credentials.
## Deploying Applications
### Managed Mode