Selected Work / Volkswagen

Engineering across cloud generations.

An evolving shared platform for Volkswagen business units: from AWS to GKE, combining software engineering and long-term operational responsibility.

Engineering Evolution

From Kops through EKS to GKE.

The diagram shows successive development phases, not a single simultaneous deployment.

Kops / AWSAmazon Web ServicesGolang
AWS / EKSAmazon Web ServicesKubernetesTerraform
GCP / GKEGoogle CloudKubernetesPulumi
Apps: Go, Node, PythonIaC: Terraform · PulumiPlatform: Kubernetes

Challenge

Multiple business units and development teams needed shared, governed platform capabilities without excessive infrastructure dependencies.

Architecture

First AWS with Kops, followed by EKS and Terraform. Subsequent evolution moved to Google Cloud with GKE and a custom versioned Pulumi/TypeScript framework.

Engineering

Java and Node.js engineering alongside some Python. The GKE platform combines Flux GitOps, Crossplane self-service, Kong API gateway, Kyverno, External Secrets, mTLS and network policies.

Outcome

A shared standardized platform supporting self-service, declarative deployments, tenant-specific observability and technical security and governance controls.

Engineering Evidence

Infrastructure is software.

The published GKE architecture documents an object-oriented Pulumi framework distributed as a versioned NPM package, Flux delivery, Crossplane resources, and Prometheus/Grafana observability.

Explore our engineering method ↗

The historical AWS phase and later GKE evolution represent different architecture states. Work involved partners and Kubernauts colleagues; engagement and responsibility boundaries should remain explicit.

Your challenge. Our engineering.

Let's discuss what matters.

Discuss a project