DevOpsArk + Argo CD
Read existing Argo applications, or take over reconciliation
Vendor: CNCF
What does the DevOpsArk Argo CD integration do?
The DevOpsArk Argo CD integration reads applications, sync status and health from an existing Argo CD installation into the DevOpsArk inventory, and can add metric-gated progressive rollouts on top or take over reconciliation entirely.
What the Argo CD integration provides
- Import Argo CD applications, projects, sync status and health into the DevOpsArk inventory.
- Correlate Argo sync events with metrics, logs and alerts on one timeline.
- Add metric-gated progressive rollouts and automatic rollback to Argo-managed applications.
- Report drift and out-of-sync applications alongside the rest of the estate.
- Migrate applications to ArkCD reconciliation incrementally, one at a time.
Exactly what is read, and what can be written
Read and write are separate grants. Nothing in the write column happens unless you explicitly allow it.
- Argo CD applications, projects and their source references
- Sync status, health status and operation history
- AppProject role and destination restrictions
- Sync and rollback operations where write scope is granted
- Rollout progression signals for gated deployments
Connecting Argo CD
- 1Connect Argo CD
Provide the Argo CD API endpoint and a read-only account token.
- 2Import applications
Applications, sync status and health appear in the DevOpsArk inventory.
- 3Add gates if wanted
Attach metric gates and automatic rollback to selected applications.
- 4Migrate selectively
Move reconciliation to ArkCD one application at a time, with no big-bang cutover.
Which modules use Argo CD
Argo CD integration: frequently asked questions
No. DevOpsArk can read an existing Argo CD installation so its applications and sync status appear in one inventory alongside everything else, and can add progressive rollout gates without changing how Argo reconciles.
Metric-gated progressive rollouts with automatic rollback, correlation of sync events with metrics and logs, cross-cluster inventory beyond the applications Argo manages, and cost and security context on the same objects.
Yes. Migration happens application by application, so both can reconcile different applications in the same cluster during the transition.
Existing Argo Rollouts resources are read and reported. ArkCD provides equivalent progressive delivery natively, so teams generally use one or the other per application rather than both.
Integrations that commonly go with this one
Connect Argo CD and see your own data
Read-only connection takes minutes. Most demos start with the customer estate rather than a sample one.