[Reference Architecture] GitOps-Native Multi-Cluster Kubernetes Platform for EU Data Sovereignty

### Name

Multi-Cloud GitOps Platform at Obmondo — EU Data Sovereignty, Zero Vendor Lock-in

### Organization

Obmondo

### Team(s)

- Platform Engineering
- SRE
- Customer Operations

### Overview and Goals

Obmondo operates production Kubernetes for multiple customers across AWS, GCP, Azure, Hetzner, and bare metal with a team of under 10 engineers. The goal was to eliminate snowflake clusters: every production failure fixed once in KubeAid propagates to every cluster on the next ArgoCD sync. Secondary goal: full EU data sovereignty with no vendor control plane, no proprietary APIs, and identical configuration on bare metal in Germany, on-premises in customer datacentres, and EU-region cloud VMs.

### Projects

Kubernetes, ArgoCD, Helm, Prometheus, Alertmanager, Cilium, cert-manager, Cluster API (CAPI), Velero, Traefik, Sealed Secrets (Bitnami), kube-prometheus, OpenTelemetry

### Planned Evolution

- Expanding Cluster API support to additional bare metal providers
- Deeper OpenTelemetry integration for distributed tracing across workloads
- Automated compliance reporting (GDPR, NIS2, ISO 27001) from Prometheus metrics
- Broader FQDN egress policy coverage in Cilium across all KubeAid chart defaults