Designing a Reliable Kubernetes Deployment with GitOps

说明与用途

该项目展示了如何将 CI 与 GitOps 结合，实现可靠的 Kubernetes 部署：CI 发布镜像版本，GitOps（由 Argo CD 管理）应用选定版本，确保发布透明度和控制。

问题

Deployments become difficult to trace, inconsistent, and teams lose visibility into which application version is actually running when artifact versioning, deployment configuration, and release decisions are not explicitly connected.

结果

The workflow provides explicit versioning, traceability, and release checkpoints, reducing the risk of unreviewed changes reaching production.

工作流

• 1. Commit Go code to application repo. 2. CircleCI builds the image and pushes it to Harbor. 3. After successful build, a reviewer manually updates the image tag in environments/production/values-prod.yaml in the GitOps repo. 4. Argo CD detects the change and shows a diff. 5. Reviewer manually triggers Sync in Argo CD to apply the new image to the cluster.
• 6. Kubernetes schedules and runs the updated workload.
• 7. Health endpoint /health is used to verify deployment.

证据

Without an explicit workflow, deployments can become difficult to trace, inconsistent, and teams may lose visibility into which application version is actually running.

来源

The pipeline automates image delivery, while release promotion remains explicit: a person updates the GitOps image tag to deliberately select the version to deploy, then manually starts synchronization in Argo CD to control when that version is applied to the cluster.

来源