OpenShift to EKS with GitHub Actions — multiple daily prod releases.

# BFSI Customer Story — Daily prod releases per dev

**Industry:** BFSI
**Cloud:** AWS
**Outcome:** Daily prod releases per dev

## Summary
Modernized hundreds of apps from on-prem OpenShift to AWS EKS with GitOps, granular RBAC, and a Jenkins-to-GitHub Actions migration.

## The Challenge
The client ran an on-prem OpenShift cluster supporting hundreds of applications, with CI/CD stitched together through Jenkins pipelines. They wanted to move to AWS EKS to unlock cloud elasticity and cut OpenShift licensing spend, while also standardizing CI/CD by retiring Jenkins in favor of GitHub Actions.The catch: developer productivity could not slip during the transition. Security, network controls, and day-to-day release velocity all had to improve at the same time as the platform shift.

## The Solution
CloudHedge designed and executed the migration onto AWS EKS, rebuilding the CI/CD surface around GitHub Actions workflows. Granular RBAC and tightened network rules locked down the new platform from day one, and GitOps principles made every environment change auditable and reversible.Custom dashboards, alerts, and notifications gave platform and app teams real-time observability into the new cluster, while standardized workflow templates let teams move apps across environments through pull-request merges instead of bespoke Jenkins scripts.

## The Outcome
Security and network posture improved materially through granular permissions and GitOps-controlled change. Developers can now ship multiple secure production changes per day, with code flowing through PR-driven GitHub Actions pipelines instead of hand-maintained Jenkins jobs.Observability is richer, OpenShift licensing costs are gone, and the platform team has a consistent EKS baseline to extend to future workloads — all without compromising the release cadence during the cutover.


## Stack
- AWS
- EKS
- GitHub Actions
- GitOps
- ArgoCD



## Contact
Book a demo: /contact/
Email: hello@cloudhedge.io