Client Overview

The customer is a large financial institution running BMC Helix — its enterprise IT service and operations management platform — across three dedicated VMware Kubernetes environments: Production Data Centre, Disaster Recovery, and UAT, with DR actively exercised multiple times every quarter.

As VMware's own Kubernetes roadmap moved forward to VMware vSphere Kubernetes Service (VKS), the bank needed a credible, low-risk path to modernize the platform beneath BMC Helix without disrupting a service its IT operations teams depend on daily.

Challenges Faced

• The Kubernetes generation underneath BMC Helix was ageing out of VMware's roadmap, leaving no viable option to simply stand still.
• Production, DR and UAT run as three dedicated clusters, and any migration approach had to hold together across all of them without blurring the boundaries between them.
• BMC Helix already moves between DC and DR multiple times a quarter, so migration could not be allowed to disrupt that operating rhythm.
• Namespaces, persistent data, storage, ingress, secrets, certificates, monitoring and backup all had to move together — Kubernetes migration is never just cluster migration.
• Every change needed to meet the operational and governance standards expected inside a large financial institution.
• BMC Helix supports the teams who run enterprise IT operations, leaving no tolerance for extended or unplanned outages.

Solutions Provided

• Mapped BMC Helix's complete footprint across all three environments before recommending any migration sequence.
• Designed a phased migration path — UAT, then DR, then Production DC — so the approach is validated on lower-risk environments before it touches production.
• Migrated Kubernetes objects, configurations, persistent data, storage integration, networking, ingress and load-balancing to VKS, environment by environment.
• Carried forward and re-validated security policies, certificates, secrets and access controls on the new platform.
• Preserved and adapted the DC-DR switchover procedures and operational runbooks so BMC Helix kept moving between sites throughout the migration.
• Fed operational experience from the UAT and DR migrations back into a de-risked plan for the Production DC transition.

Outcomes

• UAT and DR are now fully migrated and running on VMware VKS.
• The bank's quarterly DC-DR switchover model was preserved and exercised throughout the migration, including during upgrade cycles.
• Production DC migration risk has been reduced by lessons already learned on UAT and DR.
• Security policies, certificates and secrets were carried forward and re-validated on the new platform.
• Governance standards were maintained across every migrated environment.
• Sunfire has now implemented BMC Helix across three large banking organizations, extending a track record of end-to-end Kubernetes lifecycle ownership.