← All insightsIntegration

How to use Red Hat OpenShift with Helm

CodeWizard Engineering · 3 April 2025 · 3 min read · Intermediate

Red Hat OpenShift and Helm are a common pairing in a modern DevOps stack. Here is how they fit together and a practical way to wire them up.

Where Red Hat OpenShift fits

OpenShift is Red Hat's enterprise Kubernetes distribution, adding integrated CI/CD (Pipelines/Tekton), image builds, stricter security defaults (SCCs), a developer console and a curated operator ecosystem.

yaml
apiVersion: route.openshift.io/v1
kind: Route
metadata: { name: web }
spec:
  to: { kind: Service, name: web }
  port: { targetPort: 3000 }
  tls: { termination: edge }

Where Helm fits

Helm packages Kubernetes manifests into versioned, parameterized 'charts' so you can install, upgrade and roll back an entire application with a single command and a values file.

yaml
# templates/deployment.yaml
spec:
  replicas: {{ .Values.replicaCount }}
  template:
    spec:
      containers:
        - name: {{ .Chart.Name }}
          image: "{{ .Values.image.repo }}:{{ .Values.image.tag }}"
---
# values.yaml
replicaCount: 3
image:
  repo: ghcr.io/acme/web
  tag: "1.0"

Making them work together

  • Work with SCCs - run non-root and drop capabilities
  • Use ImageStreams + DeploymentConfigs/Deployments for rollouts
  • Pin dependency versions in Chart.yaml and commit Chart.lock
  • Use --atomic and --wait so failed upgrades roll back automatically

Want this pairing set up properly, with docs and handover? That is exactly the kind of work CodeWizard's embedded senior engineers do - and both Red Hat OpenShift and Helm have active community groups you can join for free.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult