Push-based deployment applies GitOps configuration changes from a deployment pipeline to a specified running environment. A commit triggers application-image construction and manifest generation; merging those manifests into the configuration repository triggers deployment. section 9.4.1
A typical workflow is:
- Commit application code, triggering the deployment pipeline. section 9.4.1
- Build the application container and generate deployment manifests from templates. section 9.4.1
- Store generated manifests and API gateway configuration in the configuration repository. section 9.4.1
- Merge changes to the mainline, causing the pipeline to apply the target state. section 9.4.1
Version control provides an audit history and transaction log: reverting a commit can roll back the environment, while earlier or later states can be redeployed. The model requires target-environment credentials in the CI/CD system, creating a security risk if that system is compromised. section 9.4.1 section 9.4.1
Figure 9.6 GitOps push-based deployments
Trace the repository, pipeline, manifest, and running-environment flow. section 9.4.1
