Argo CD
gitopsargo-cdGitOps
GitOps controller reconciles desired state from main.
Technical Summary
Application points at repo path or Helm chart that builds/serves Navo. Automated sync with prune; manual for regulated envs.
Advantages
- Clear role in the GitOps zone of the map
- Topology and narrative stay in versioned architecture YAML
- Visible to unlimited viewers without a platform portal seat
Who / What / When / Where / Why
- Who
- GitOps owners and on-call for Argo CD
- What
- GitOps controller reconciles desired state from main.
- When
- Continuous — part of the always-on architecture map
- Where
- CLI pipeline automation · GitOps
- Why
- Documents how Argo CD connects in the living map so teams share one Git-backed model.
Related Services
Related Repos
argo-cd-servicepipeline-platform
Links
Argo CD runbook
wiki/wiki/argo-cd.md
In-app wiki path (demo stub)
Source repository
repohttps://example.com/repos/argo-cd
Example repo link for the public demo
Ops dashboard
urlhttps://example.com/dashboards/argo-cd
Add Service Link
DevIn the full Navo app (local pnpm dev), this form writes links into architecture YAML. On the public website it is disabled.
Local annotations (overlay)
In Navo, notes and personal links stay in browser localStorage until you export for a PR. Overlay editing is off in this public demo.
Ready to contribute in a real deployment? Architecture maps ship through Git PRs — not browser-only edits. Share & export docs