Bestcloudfor.me - banking client, 2025
Regulated Multi-Cloud Estate
A bank's monolith became microservices without giving up the requirement that it survive losing a cloud provider.
- Clusters
- 3
- Cloud providers
- 2
- Servers auto-patched
- 50+
- Problem
- Legacy monolithic systems in a regulated banking environment had to become a containerised microservice architecture. Regulation meant the estate also had to keep running if an entire cloud provider became unavailable, which ruled out a single-region answer.
- Approach
- Three clusters with distinct jobs: a large production cluster on Oracle Cloud, a cross-provider disaster recovery cluster on Huawei Cloud, and a dedicated control plane cluster running the platform's own applications. The Kubernetes API and ingress sit behind a virtual IP served by a two-node HAProxy and Keepalived pair, carrying both north-south and east-west traffic. Delivery is GitOps; OS patching is generated from Qualys scan data and applied through a single Ansible dynamic-inventory run.
- Outcome
- The migration ran with automated CI/CD and GitOps delivery, monitoring and logging through Prometheus, Grafana and the ELK stack, and a DR path that does not depend on the primary provider being reachable.
- RKE2
- ArgoCD
- Ansible
- Prometheus
- Grafana
- ELK
- Redis
- Oracle Cloud
- Huawei Cloud
- Linux
