A Kubernetes manifest is a declarative document describing the desired state of Kubernetes resources. In an ML deployment workflow, CI/CD generates or updates manifests that reference the newly built service image, and applying them deploys the updated service. section 1.3.3
Manifests provide the operational contract between deployment automation and the Kubernetes cluster:
- Reference the container image produced by CI/CD and stored in a container registry. section 1.3.3
- Declare resource settings such as a service type, allowing Kubernetes to expose the application as ClusterIP or LoadBalancer. section 3.4.2
- Act as the expected state that Argo CD compares with the live manifest and synchronizes from Git. section 3.4.2
Detecting configuration drift
After deployment, changing the fast-api-app service from ClusterIP to LoadBalancer makes Argo CD report the application as out of sync. Its diff identifies the service type as the difference between the live and expected manifests. section 3.4.2
Figure 3.14 Argo CD ensures that the manifests in Git and the ones deployed in K8s match.
Use the diagram to inspect how Argo CD keeps Git manifests and deployed Kubernetes resources aligned. section 3.4.2
