Skip to main content
What you’ll get: ewake can read your Argo CD applications — their sync status, health, and the revision each one has deployed — so it can tell whether a recent rollout lines up with an incident and surface applications that are out of sync or degraded. Access is read-only.

​
Prerequisites

  • An Argo CD instance reachable from ewake — the API server URL, e.g. https://argocd.yourcompany.com
  • Admin access to create a local account and bind it to a read-only role
ewake authenticates with an Argo CD API token scoped to a read-only account. It only ever reads — it never syncs, rolls back, or edits any application or Argo CD configuration.

​
Configuration

1

Create a read-only local account

In your Argo CD argocd-cm ConfigMap, add a local account with the apiKey capability:
Then bind it to Argo CD’s built-in read-only role in the argocd-rbac-cm ConfigMap:
Use the built-in role:readonly (or a policy limited to get). Don’t grant sync, create, update, delete, or override — read-only access is what keeps ewake unable to change your deployments.
2

Generate an API token

Generate a token for the account:
Copy the token now — you’ll paste it into ewake in the next step.
3

Get your Argo CD server URL

Use the base URL of your Argo CD API server, e.g. https://argocd.yourcompany.com — the same host you use for the Argo CD UI or argocd login.
4

Open the Argo CD integration in ewake

In your ewake dashboard, go to Integrations → Infrastructure → Argo CD → click Connect with token.
5

Enter your credentials

6

Test and save

Click Test connection to verify the connection, then click Save.
Argo CD is connected. Ewake can now read your application delivery state during investigations.
Ewake uses read-only Argo CD API calls. It never syncs, rolls back, or modifies any application or Argo CD configuration.