Continuous deployment automates the release of tested application changes, replacing error-prone manual deployments with a repeatable path from code change to production service. section 3.4 section 3.6
A production-oriented deployment flow typically:
- Tests the application, builds a container image, and updates the Helm chart with the new image. section 3.4
- Deploys the updated chart to Kubernetes using the newly built image tag. section 3.4
- Monitors the deployed version and restores the latest intended image when an older deployment appears. section 3.4
GitLab CI and Argo CD
A GitLab CI job tests and builds an ML application, then updates its Helm chart. Argo CD deploys that chart to Kubernetes and monitors whether the running image matches the latest build. section 3.4
Figure 1.9 Model deployment consists of the container registry, CI/CD, and automation working in concert to deploy ML services.
Shows the container registry, CI/CD automation, and deployment workflow working together to release an ML service. section 1.3.3





