v2.5 and after
Argo Workflows ships with a server that provide more features and security than before.
The server can be configured with or without client auth (server --auth-mode client). When it is disabled, then clients must pass their Kubeconfig base 64 encoded in the HTTP Authorization header:
ARGO_TOKEN=$(argo auth token)
curl -H "Authorization: $ARGO_TOKEN" https://localhost:2746/api/v1/workflows/argo
- Learn more on how to generate an access token.
API reference docs :
- Latest docs (maybe incorrect)
- Interactively in the Argo Server UI. (>= v2.10)