You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1.6 KiB
1.6 KiB
| title | description |
|---|---|
| ArgoCD | ArgoCD Widget Configuration |
Learn more about ArgoCD.
Allowed fields (limited to a max of 4): ["apps", "synced", "outOfSync", "healthy", "progressing", "degraded", "suspended", "missing"]
widget:
type: argocd
url: http://argocd.host.or.ip:port
key: argocdapikey
You can generate an API key either by creating a bearer token for an existing account, see Authorization (not recommended) or create a new local user account with limited privileges and generate an authentication token for this account. To do this the steps are:
- Create a new local user and give it the
apiKeycapability - Setup RBAC configuration for your the user and give it readonly access to your ArgoCD resources, e.g. by giving it the
role:readonlyrole. - In your ArgoCD project under Settings / Accounts open the newly created account and in the Tokens section click on Generate New to generate an access token, optionally specifying an expiry date.
If you installed ArgoCD via the official Helm chart, the account creation and rbac config can be achived by overriding these helm values:
configs:
cm:
accounts.readonly: apiKey
rbac:
policy.csv: "g, readonly, role:readonly"
This creates a new account called readonly and attaches the role:readonly role to it.