Platform · GitOps · Operations

DevOps solutions for production Kubernetes.

Design, operate, and evolve platforms: GitOps with Argo CD, cloud and on-prem Kubernetes, TLS-automated edge, observability, and a data plane. The same bar as an environment that cannot go down.

See services Read the architecture

What I deliver

From the GitOps repo to the cluster. No theatre — patterns that survive incidents.

GitOps

ApplicationSets, overlays, promotion by tag. The cluster converges; nobody kubectl-applies YAML.

Kubernetes

EKS, on-prem, and lab Kubernetes. Cilium, Gateway API, autoscaling. One catalog, many destinations.

Edge

Ingress or Gateway, cert-manager, external-dns. Hostname and certificate as platform concerns.

Observability

Metrics, logs, and cost on one surface. Node agents, remote write to the backend.

Data plane

Kafka, CDC, MQTT, Redis, Postgres with an operator. Same GitOps as the APIs.

Platform

Registry, secrets, CI → Git contract. The pipeline is not the deploy.

How I work

01
Git as the source of truth

The cluster follows the repo. Per-environment overlays, promotion by image tag, self-heal against drift.
02
Minimal diff, operable defaults

Shared base, overlay only for what changes. Secrets stay out of Git. Charts resolve at sync, not vendored.
03
Many destinations, one catalog

Cloud Kubernetes, on-prem, and lab clusters in the same model: ApplicationSet, namespace, destination. No hand-copied clusters.

Need a platform your team can actually run?

A straight conversation about current state, gaps, and the path to continuous GitOps.

Get in touch