CI/CD Boundary

CI completes when an approved immutable image and its evidence are published to ECR, ACR, or the Snowflake image registry. It does not mutate Kubernetes manifests, call cluster APIs, or decide deployment health.

CD begins when Argo CD Image Updater observes an eligible image according to environment policy. Argo CD reconciles the declared application and Kubernetes reports health. This separation allows application CI to remain consistent while EKS, AKS, and SPCS deployment mechanisms evolve independently.

flowchart LR
  CI[CI: validate, build, scan, publish] --> Registry[Registry]
  Registry --> Updater[Argo CD Image Updater]
  Updater --> GitOrApp[Configured update method]
  GitOrApp --> Argo[Argo CD reconciliation]
  Argo --> Cluster[EKS / AKS]