Kubernetes

Helm, Flux and Argo CD (GitOps)

GitOps means the cluster's desired state lives in a Git repository and a controller inside the cluster keeps reality matching it. No one runs kubectl apply from a laptop. Changes are pull requests, rollbacks are reverts and the audit trail is the commit log.

We build GitOps pipelines with Flux (our default) or Argo CD, package applications as Helm charts or Kustomize overlays, and wire image automation so a merged PR becomes a running deployment.

At a glance

ControllersFlux, Argo CD
PackagingHelm, Kustomize, OCI artifacts
SecretsSOPS, Sealed Secrets, External Secrets Operator
PromotionEnvironments as branches or directories, image automation

What RackLedge does

How we work

Every cluster we build starts from Git. Infrastructure as code creates the cluster, Flux or Argo CD reconciles everything inside it, and no change reaches production without a pull request. That is what makes a rebuild after a bad day a matter of hours instead of weeks.

Operations are the product: monitoring with alerts that mean something, backups of cluster state and persistent volumes, upgrades on a quarterly cadence and an on-call engineer who already knows the environment. We run production Kubernetes for our own platforms, so the runbooks are ones we use ourselves.

We are honest about fit. A handful of stable services on a couple of VMs does not need Kubernetes, and we will say so. Teams that ship weekly, need to scale or run many services get real value from it.

Related services

More on kubernetes

Frequently asked questions

Flux or Argo CD?

Both are solid. Flux is lighter and composable; Argo CD has a stronger UI. We default to Flux and deploy Argo CD when a team wants the console.

Need a hand with this?

Tell us what you are running and what is slowing you down. You get a straight assessment and a plan, with no obligation. Support desk is staffed 24/7.

Get in touch