RAMATECHInnovation

Financial services · On-prem air-gapped network

Helm and GitOps for a Production App on Air-Gapped OpenShift

Packaged an application already running in production as a Helm chart and moved it to Argo CD GitOps on an air-gapped OpenShift cluster, without disrupting production.

Financial services enterprise (name withheld). Delivery experience of the Ramatech team; the client name is withheld under confidentiality.

Architecture overview. Hover to animate the flow.

Challenge

A production application on an air-gapped OpenShift cluster was deployed with hand-maintained YAML and oc commands. Every production change was manual and risky, and configuration differed between environments.

What we did

Created a Helm chart for the application from its running configuration, with per-environment values kept in GitLab. Set up Argo CD to sync the chart to the cluster, with Jenkins in the delivery path and container images served from a mirror registry inside the air-gapped network. The application moved to the new model while production kept running.

Results

  • Helm + GitOps

    Production app moved without disrupting production

  • Consistent

    Same configuration model across environments

  • Traceable

    Every production change recorded in Git, with simpler rollback

Stack

  • OpenShift
  • Air-gapped
  • Helm
  • Argo CD
  • GitLab
  • Jenkins
  • Mirror registry

Planning similar work?

We reply within one business day (Mon–Sat, 10:00–19:00 IST).