Case studies

A bank’s integrations on a Kubernetes platform its own team runs

Tamarisk Trust Bank’s payment and channel integrations ran on individually maintained servers and manual releases. We moved them onto an upstream Kubernetes platform with GitOps delivery, and trained the bank’s engineers to run it.

Client
Tamarisk Trust Bank
A fictional retail and commercial bank serving customers across Lagos and the south west.
A developer at a desk writes code on a large monitor and a laptop

Results

The numbers that moved

release cadence for Tamarisk’s integration services
Monthly to daily
of payment reconciliation exceptions matched automatically
92%
to rebuild the platform from Git in a recovery rehearsal
Under 2 hours

Challenge

What was in the way

Tamarisk Trust Bank connects its core banking system to card, transfer and mobile channels through integration services that had grown up over a decade. They ran on individually maintained servers, and every release was a manual, out-of-hours exercise that only two engineers fully understood.

Reconciliation suffered as a result. When a transaction failed between systems, finding where it had stopped meant searching several logs by hand, and the audit team wanted a clear record of every change made to production.

Approach

How we worked

We started with a review of the integration estate and agreed with the bank’s infrastructure team which services would move first. The platform was built on upstream, unforked Kubernetes with Talos Linux, Flux for GitOps, Kyverno for policy as code and FreeIPA for central identity, hosted across the bank’s two data centres.

Every change to the platform and its workloads now goes through Git. We rebuilt the integration services with monitoring and message tracing, moved them across in stages, and worked alongside the bank’s engineers so that they own the platform day to day. Support for the underlying projects is provided through k8s.ng.

Outcome

What changed

Releases that once needed a weekend window now ship during the working day, and each one is a reviewed change that can be reverted. Failed transactions can be traced from entry to exit in one place, and the audit team can read the history of the platform directly from the repository.

The bank’s own team runs the platform, with Cloud Remark available for escalation and lifecycle support.

Services involved

Have a similar problem? Tell us about it.

Talk to us