Financial institutions are moving core banking, payment processing, and trading systems to Kubernetes. DORA demands that this infrastructure meets the highest operational resilience standards. Here's how to build a Kubernetes platform that satisfies DORA without sacrificing developer velocity.
DORA-Driven Kubernetes Architecture
Multi-Cluster Resilience
Single-cluster Kubernetes doesn't satisfy DORA's availability requirements for critical functions:
- Active-active clusters across availability zones (minimum)
- Cross-region cluster federation for critical workloads
- Automated cluster failover with health-based routing
- Cluster-level chaos testing (simulate entire cluster loss)
Security Hardening
- Pod Security Standards enforced at the namespace level (restricted profile for production)
- Network policies with default-deny and explicit allow rules
- Service mesh (Istio, Linkerd) for mTLS, traffic encryption, and observability
- Runtime security monitoring (Falco, Tetragon) for threat detection
- Image signing and verification (Sigstore/cosign) — unsigned images blocked
Audit and Compliance
- Kubernetes audit logging to immutable storage
- RBAC with least-privilege, regularly reviewed
- Policy-as-code (OPA/Gatekeeper, Kyverno) enforcing DORA-relevant policies
- Automated CIS Kubernetes Benchmark scanning
Platform Engineering for DORA
Build golden paths that make DORA compliance the default:
- Namespace provisioning with pre-configured security policies, resource quotas, and monitoring
- Deployment templates with health checks, resource limits, and disruption budgets
- Automated secret rotation via external secrets operators
- Built-in observability (metrics, logs, traces) for every workload
Kubernetes Recipes
Practical guide for container orchestration and deployment — hands-on patterns you can use today.
View on Amazon →The Platform Team's DORA Responsibilities
The Kubernetes platform team owns DORA compliance for the platform layer. Application teams own their workload resilience. Clear responsibility boundaries, shared tooling, and automated enforcement — that's the model that scales.
Luca Berton