/Glossary · DevOps
What is GitOps?
GitOps is an operating model in which Git is the single source of truth for the desired state of infrastructure and applications. An agent continuously compares that state with the live environment and reconciles it automatically.
How GitOps works
Kubernetes manifests, Helm charts or Kustomize configurations live in a repository. A controller such as Argo CD or Flux, installed in the cluster, watches that repository and applies changes when a pull request is merged. If someone changes something by hand, the controller detects the difference and reverts it.
Unlike a pipeline that pushes changes with admin credentials, in GitOps the cluster pulls the changes. CI only builds the image and updates the version in Git. That reduces the permissions your CI system needs and leaves an auditable history of every deployment.
When GitOps makes sense
GitOps shines with Kubernetes and its declarative model, especially with several clusters or environments on Amazon EKS that need to stay consistent. It also adds a lot in regulated industries, because every production change is tied to a commit, an author and a reviewable approval.
For workloads on Lambda or ECS without Kubernetes, the pure model is less common; there, infrastructure as code and well-designed pipelines are usually enough. You can apply the same principles, such as declarative state and changes through pull requests, without a reconciliation controller.
Best practices and common mistakes
Keep application code and environment configuration in separate repositories, promote between environments through pull requests, and manage secrets with External Secrets Operator connected to AWS Secrets Manager. Define projects and permissions in Argo CD so each team can only deploy to its own namespaces.
Common mistakes: storing secrets in plain text in Git, turning off automatic reconciliation and ending up with drift, or cramming hundreds of applications into one repository with no structure. Another is not monitoring sync status, which leaves failed deployments unnoticed.
/FAQ
Questions about GitOps
Another question? Write to hello@nubent.com and an engineer will answer.
What is the difference between GitOps and CI/CD?
CI/CD describes the flow of building, testing and deploying. GitOps is a specific way to handle deployment: the desired state lives in Git and an agent in the environment reconciles it. They complement each other, because CI still builds and tests the artifacts.
Argo CD or Flux?
Both are CNCF graduated projects and solve the same problem. Argo CD offers a very complete web UI and an intuitive application model. Flux is more modular and lightweight. The choice usually comes down to your team's preference and experience.
Can you use GitOps outside Kubernetes?
Yes, although it is less common. Tools like Crossplane or AWS Controllers for Kubernetes let you manage cloud resources with the same model. Outside Kubernetes, the usual approach is to apply the principles with Terraform and pipelines that run reviewed plans.
How we help with GitOps
Kubernetes on Amazon EKS
Amazon EKS clusters with Karpenter, Helm and Argo CD, pod-level security and zero-downtime upgrades, run through Terraform and GitOps.
Learn morePlatform Engineering
An internal developer platform on AWS with golden paths, Backstage and Terraform self-service, for autonomous teams that ship quickly and safely.
Learn moreDevOps as a Service
An ongoing external DevOps team for your AWS infrastructure: Terraform, CI/CD, security, costs and on-call coverage, on a monthly subscription.
Learn moreNext step
What should we build next on AWS?
30 minutes with an engineer. Concrete next steps, whether or not you work with us.