Argo CD

Continuous delivery component for deploying Foundation changes.

Agentic Friendly

Component Category

Continuous integration and delivery / continuous delivery

Component Description

Argo CD is a GitOps continuous delivery platform for deploying and synchronizing Kubernetes applications.

Why It Is Used

In BullSequana AI Foundation, Argo CD helps keep deployed platform state aligned with version-controlled configuration, making delivery more automated, auditable, and repeatable. It is the preferred deployment control point for platform components and use cases that follow the GitOps model.

Learn More

Deployment notes

Argo CD deploys into the argocd namespace as the bootstrap component in the reqs tier, before all other platform components. It runs the application controller, server, and repo server as separate pods. SSO is configured through Keycloak OIDC with admin and read-only RBAC roles. Argo CD is installed with bsqai helm-apply argocd rather than synchronized from Git, so changes to the base domain, the Keycloak realm, or Argo CD settings take effect after that command runs again. See Argo CD configuration changes. Its public route is rendered by the Gateway API component, because Argo CD is installed before the Gateway API resources exist. Custom health checks are defined for CNPG clusters, CRDs, nested Argo CD Applications, and PersistentVolumeClaims: a Pending PVC counts as healthy, so that storage classes that bind on first consumer do not block a sync wave.

With [network_policy] enabled = true, the default, the argocd-network-policies component (common tier, sync wave 1) limits Argo CD egress to cluster DNS, the Kubernetes API, the Git, registry, and configured proxy ports, and the other Argo CD pods. Only Argo CD's own pods and Prometheus reach its pods, and argocd-server accepts traffic from the gateway. See Network policies.

Interacts With

  • Git service, which stores the rendered GitOps manifests.
  • OCI registry, which stores Helm charts and workload images.
  • Keycloak, for SSO and access control in the Argo CD UI. The Keycloak application sets up the argocd client after Keycloak syncs.
  • Gateway API and External DNS, to expose Argo CD through the platform ingress layer.
  • Platform components, because Argo CD is the GitOps delivery engine that synchronizes their desired state.

On this page