Architecture overview
Lab topology
Section titled “Lab topology”Build vs deploy stages
Section titled “Build vs deploy stages”One GitOps
Declarative delivery from Git — manifests live in a repository; Argo CD applies changes on sync. repo (pulse-deploy), two Argo CD Applications, plus a kpack Image that is not an Application:
Repositories
Section titled “Repositories”| Repo | Consumer |
|---|---|
pulse-app |
kpack Kubernetes-native build service that runs CNB builds on-cluster and pushes images to a registry. builds from source |
pulse-deploy |
Argo CD Argo CD — GitOps controller that syncs cluster state from Git repositories. — Application kpack ( path: kpack) and Application pulse (path: .) |
See IAM map for CodeCommit, ECR, and Argo CD auth. IRSA
IAM Roles for Service Accounts — pods use a Kubernetes service account annotated with an IAM role ARN. on kpack-sa is one path; kpack still needs an ECR docker-registry secret to push.
demo/ layout
Section titled “demo/ layout”demo/app and demo/deploy are published to the CodeCommit
AWS managed Git hosting — GitHub alternative used for app source and deploy manifests in this lab. repos above. Platform templates and demo/.generated/ stay local until you run the lab.