Argo CD or Flux: which fits us?

Both reconcile the cluster with a desired state in Git (Argo CD, Flux). The choice follows the team's knowledge and the scope of the platform. The Argo CD vs. Flux guide contains the decision rule.

What does GitOps mean?

The desired state of the cluster lives in Git and a controller keeps the cluster in sync with that source. Changes go through Git and are traceable in the history.

Does GitOps replace our CI pipeline?

As a rule, no. Existing CI pipelines stay in place for build and test, and GitOps takes over deployment.

What does introducing GitOps cost?

There is no list price for the introduction. It runs as a project through platform engineering; scope and fee are agreed after an initial assessment.

Does WZ-IT also run Argo CD as an application?

Yes, Argo CD is available as a hosted application. Offer and scope are on the page Argo CD hosting and operations.

Introduce GitOps with Argo CD or Flux

In short: the desired state lives in Git and a controller reconciles the cluster with it. We introduce Argo CD or Flux with repository structure, promotion between environments and drift detection.

Argo CD or Flux
Repository structure and promotion
Drift detection
Secrets concept and recovery

Request GitOps View scope

Reviews

IT Beratung Service Consulting Soforthilfe

Companies worldwide trust WZ-IT

Read client reviews

Starting point

When GitOps is missing

Typical situations in which changes to the cluster are no longer traceable.

Changes without a trace
Deployments run through kubectl or scripts. Nobody can say which state in the cluster is the approved one.
Environments drift apart
Test and production have different configuration, and promotion between environments is manual work.
Secrets without a concept
Credentials sit in the repository, in pipelines or with individual people only.
The tool choice is open
Argo CD and Flux solve the same task differently. The decision depends on team and platform.

Services

What the GitOps introduction covers

Introduction and handover of GitOps in a Kubernetes cluster. Broader platform topics belong to platform engineering.

Introduce

Choose Argo CD or Flux
The choice follows the team's knowledge and the scope of the platform. The decision rule is in the guide.
Repository structure and promotion
Layout of the repositories and promotion of approved states between environments.
Secrets concept
A way to handle secrets without plaintext in the repository.

Operate

Drift detection
Deviations between Git and the cluster become visible and traceable.
Recovery and handover
Every platform building block gets an owner, documentation and an upgrade path.

CI/CD pipelines, templates and policies belong to platform engineering. This page covers GitOps only. Argo CD as a hosted application is described under Argo CD hosting and operations.

Process

Four steps to GitOps

From the current state of deployments to handover to the team.

01
Record the current state
Environments, repositories and how deployments are done today.
02
Define tool and structure
Argo CD or Flux, repository structure and promotion path.
03
Set up synchronization
The controller synchronizes approved states into the environments.
04
Hand over
Owner, documentation and upgrade path for the platform building blocks.

Assessment

In-house or supported GitOps

GitOps is not a large project as long as cluster, team and applications are manageable.

In-house

In-house operation is enough when

one cluster is looked after by a team that knows Argo CD or Flux
deployments run reproducibly from Git and deviations are noticed
secrets concept and recovery have been tested

Support

Support makes sense when

several environments or clusters exist without a common structure
the choice between Argo CD and Flux is open
no owner and no upgrade path is defined for the controller

Entry point

GitOps as a project through platform engineering

The introduction runs as a project. There is no list price for it: scope and fee are agreed after an initial assessment.

View platform engineering Request GitOps

All prices are net and exclude statutory VAT. The offers are addressed to businesses. As of October 2026.

Adjacent

Hosted application

Argo CD hosting and operations

Argo CD as a hosted application from WZ-IT, offer and scope on its own page.

View Argo CD →Cluster operations

Managed Kubernetes

Operation of the cluster underneath: control plane and add-ons, upgrades, backups with restore tests and 24/7 monitoring, from €590 excl. VAT per cluster and month.

View operations →

Frequently asked questions

Answers to the most important questions

Knowledge

Guides and sources on GitOps

Tool comparison, documentation and adjacent services.

Guides

Primary sources

Related services

Reviews & projects

Operations that visibly relieve customers

Customer feedback on monitoring, updates, maintenance, support and stable production systems.

Networking & Provisioning

WZ-IT moved our studio infrastructure from decentralised individual devices to a central platform: every site is securely connected via VPN, new devices are onboarded automatically and an entire site is provisioned from a template, without manual steps on location. What impressed me most is the breadth and depth of their knowledge: Timo and Robin are not a typical IT provider who sets up a server and leaves. The two of them think their way into highly complex infrastructure and software topics, work through every requirement we put in front of them, and build networking, provisioning and operations so that everything fits together in the end. WZ-IT is an excellent partner for complex software, network and architecture projects.

Steve KirchnerManaging Director, nextGYM GmbH

View project

International

Built in Germany's Ruhr Valley. Running worldwide.

WZ-IT designs, develops and operates infrastructure and software for clients in Germany and internationally. We deliver projects remotely and continue supporting them in ongoing operations after go-live.