ArgoCD Provider
The ArgoCD provider enables you to pull topology and Application data.
Overview
The ArgoCD Provider facilitates pulling Topology and Application data from ArgoCD. ArgoCD Applications are mapped to Keep Services ArgoCD ApplicationSets are mapped to Keep Applcations
Authentication
This provider requires authentication.
- argocd_access_token: Argocd Access Token (required: True, sensitive: True)
- deployment_url: Deployment Url (required: True, sensitive: False)
Certain scopes may be required to perform specific actions or queries via the provider. Below is a summary of relevant scopes and their use cases:
- authenticated: User is Authorized (mandatory)
In workflows
This provider can’t be used as a “step” or “action” in workflows. If you want to use it, please let us know by creating an issue in the GitHub repository.
Topology
This provider pulls topology to Keep. It could be used in correlations and mapping, and as a context for alerts and incidents.
Connecting with the Provider
- Obtain the access token from your ArgoCD instance by following
Generate auth token
from ArgoCD’s User management docs. - Set the deployment URL to your ArgoCD instance’s base URL (e.g.,
https://localhost:8080
).
Features
The ArgoCD Provider supports the following key features:
- Topology: Configures the Topology usin the applications from ArgoCD.
- Applications: Creates Applications using the ApplicationSets from ArgoCD.