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.

Источник