Leave request
Presentation
Burger logoBurger logo
Case study · Cluster rescue and migration

From a broken cluster to 99.98% uptime

How Digital Care rescued a government online-services platform from a failing OpenShift cluster and rebuilt it on Kubernetes.

Industry Government servicesWorkload Public online servicesStack Kubernetes
A wave of light re-igniting dark server nodes across a grid.
The situation

The client operates online services used by government institutions. The platform ran on an OpenShift 3 cluster whose certificates had gone invalid: pods no longer started and nodes could not reach each other. The team had no safe way to deploy or recover, and public-facing services were at constant risk of going dark.

The goal

First, resuscitate: restore cluster operation quickly. Then, rebuild for good: migrate from OpenShift to Kubernetes, stabilize the infrastructure and put proper CI/CD underneath.

Before
Expired
cluster certificates

An OpenShift 3 cluster with invalid, expired certificates. Pods would not start, nodes lost access to each other, and there was no safe way to deploy. Every day risked a full outage of public-facing services.

After
99.98%
infrastructure availability

A fault-tolerant Kubernetes cluster with monitoring, logging and CI/CD. Applications deploy automatically and without downtime. The old cluster is gone for good.

What we built

Rescued first. Rebuilt to last.

01

Emergency recovery

Issued new valid certificates and brought the failing cluster back to life in 4 hours, putting services back on solid ground before touching anything else.

02

A new Kubernetes home

Deployed a fresh Kubernetes cluster, moved every application onto it and destroyed the old OpenShift cluster.

03

Fault-tolerant storage

External storage built on GlusterFS: data survives node failures.

04

CI/CD on Jenkins

Automated build and deploy pipelines: applications ship to the cluster quickly, automatically and without downtime.

05

Monitoring and logging

Prometheus + Grafana across all services: availability and resource consumption visible at all times.

Cluster recovery
T+3h 58m
api-gatewayHEALTHY
citizen-portalHEALTHY
document-serviceHEALTHY
paymentsHEALTHY
notificationsFAILED
RECOVERED in 4h 02muptime since migration: 99.98%
Technologies
JenkinsKubernetesHelmPrometheusGrafanaMinioTerraformGlusterFS
Results
4 hours
to bring the failing cluster back online
99.98%
infrastructure availability
0 downtime
application deploys, fully automated
100%
workloads migrated off the dying OpenShift cluster
Next case
Paralax