GitOps
Argo CD, Flux and promotion workflows that make deployments standard, visible and reversible in every environment.
The problem
Every team deploys differently, promotion between environments is a person running a script, and nobody can see in one place what is running where or roll it back with confidence. Deployment is the least standard part of the delivery path.
What you receive
- A GitOps control plane with documented ownership and promotion rules
- Deployment visibility: what is where, since when, and why
- Promotion and rollback runbooks the team has used
- Standards for charts and overlays that new services inherit
Capabilities
- Argo CD and Flux architecture, including multi-cluster and app-of-apps patterns
- Environment promotion with Kargo where it fits, or equivalent workflows
- Helm chart and Kustomize standards
- Progressive delivery (canary, blue/green) with health-based gates
- Deployment guardrails and policy
- Rollback that is a Git operation, rehearsed
- Multi-environment management from one control plane
Example engagement
GitOps adoption for a product company with six teams and two clusters
Introduced Argo CD with an app-of-apps layout and Kargo-driven promotion, defined a service template that produced a deployable repository in minutes, and moved the teams over one at a time while the old deployment scripts were retired.
Representative of the work; client details are not published.
Technologies
- Argo CD
- Argo Rollouts
- Flux
- Kargo
- Helm
- Kustomize
- Backstage
- Port
- Crossplane
Related solutions
Build a Kubernetes platform
An enterprise Kubernetes environment with networking, security, GitOps, observability, autoscaling and operating standards.
Improve deployment reliability
Introduce GitOps, health gates, progressive delivery, observability, rollback controls and release visibility.
Build an internal developer platform
Repeatable onboarding, deployment templates, service standards, infrastructure abstractions and developer self-service.
How we think about it
Platform engineering · GitOps · CI/CD · 7 min
Golden paths that engineers actually take
A platform team's output is not the platform; it is the paths other teams take through it. How to build paved roads that are faster than the alternative, keep them honest with the people who use them, and avoid turning them into mandates.
Kubernetes · Security · Platform engineering · 8 min
Isolating tenants on a shared Kubernetes cluster
A namespace is not a security boundary, but a namespace plus five other controls is a usable one. What separates tenants on a shared cluster, what still needs a cluster of its own, and how to decide which customer gets which.
Observability · Platform engineering · 7 min
SLOs before dashboards
Observability tooling is easy to buy and hard to make useful. Start from what the service promises, measure it from the user's side, and let the alerts, the dashboards and the on-call rota follow from the promise rather than from what the tools export.
Before you write to us
The questions we get asked first.
Answered the way we would on a call. The consulting FAQ covers how engagements work in general.
- We have Argo CD. Why is promotion still manual?
- Because reconciliation and promotion are different problems. Argo CD or Flux make what runs match Git; moving a change from dev to production is a change to Git, and it needs its own controller, gates and record. That is the piece most GitOps adoptions stop short of.
- Does GitOps mean every team has to learn Kubernetes manifests?
- It should not. A paved road gives a team a template that already carries the manifests, the pipeline, the dashboard and the alerts; they edit code, and the promotion is a merge they control. The platform team owns the template so it can change every service at once.
- What access do you need?
- Read access to the GitOps repositories, the Argo CD or Flux installation, and the cluster it reconciles, and a few hours of the team's time. Nothing is run under your production credentials from outside your own tooling, and write access only arrives with an implementation phase, through your pipeline and your review.
- What happens after the engagement?
- Everything is written down and handed over: the decisions, the code, the runbooks and the reasons. Your team runs it. Where a standing arrangement makes sense, a retainer or a few architect days a month keeps the context without keeping us on the payroll.