Argo CD was used as both the GitOps deployment model and the source for read-only deployment status exposed through the adapter. Applications and a dedicated project were configured, but no live API or synchronization result was shown.
- What worked
- Existing application labels and GitOps conventions mapped cleanly to team and service metadata, and the application/project model supported the new platform components.
- What got in the way
- The existing project restrictions were too narrow for the gateway stack, requiring a new project with additional namespaced resource permissions.