All 16 CI/CD, Publishing & Deployment questions
More in CI/CD, Publishing & Deployment
What is the difference between dotnet publish's --self-contained and framework-dependent options in the context of container image builds? What is the difference between blue-green deployment and canary deployment, and how do they apply to .NET applications? How do you set up automated database migrations as part of a .NET CI/CD deployment pipeline safely? How does deployment slot swapping (e.g., Azure App Service deployment slots) enable near-zero-downtime deployments? What is the purpose of a multi-stage Dockerfile for .NET applications, and how does it reduce final image size? How do you implement automated rollback in a CI/CD pipeline triggered by post-deployment monitoring signals (error rate, latency)? What is Native AOT compilation in .NET, and what are its main benefits and limitations?
Advertisement
Back to results for “Architecture”
.NET › CI/CD, Publishing & Deployment

How does GitOps (e.g., using Flux or ArgoCD with Kubernetes) change the deployment model compared to traditional push-based CI/CD pipelines?

Advanced

Answer

In GitOps, a Git repository is the single source of truth for the desired deployment state (Kubernetes manifests, Helm charts), and a controller running inside the cluster continuously reconciles the actual cluster state to match what's declared in Git (pull-based), rather than a CI pipeline directly pushing changes to the cluster (push-based) -- this provides a full audit trail via Git history, easy rollback (revert the Git commit), and eliminates the need to grant CI systems direct write credentials to production infrastructure.
# GitOps flow:
# 1. Developer merges PR updating image tag in deployment.yaml
# 2. Flux/ArgoCD controller (running IN the cluster) detects the Git change
# 3. Controller pulls the new manifest and reconciles cluster state to match
# CI pipeline never has direct cluster write access
Real-world example A platform team adopts ArgoCD so that rolling back a bad .NET microservice deployment is as simple as reverting a Git commit, with the in-cluster controller automatically detecting and applying the reverted state within seconds, without needing direct pipeline access to production credentials.

Common follow-ups: How does GitOps improve the security posture compared to push-based deployment?;What happens if someone makes a manual, undocumented change directly to the cluster?

Docker & Containerization;Microservices & Distributed Architecture Patterns
All 16 CI/CD, Publishing & Deployment questions