← All insightsIntegration

How to use Red Hat OpenShift with Argo CD

CodeWizard Academy · 2 April 2025 · 3 min read · Intermediate

Red Hat OpenShift and Argo CD 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 Argo CD fits

Argo CD is a Kubernetes controller that continuously compares the live cluster to manifests in Git and syncs any drift, giving you declarative, auditable, self-healing deployments.

yaml
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata: { name: web, namespace: argocd }
spec:
  project: default
  source:
    repoURL: https://github.com/acme/deploy.git
    targetRevision: main
    path: apps/web
  destination:
    server: https://kubernetes.default.svc
    namespace: web
  syncPolicy:
    automated: { prune: true, selfHeal: true }
    syncOptions: [CreateNamespace=true]

Making them work together

  • Work with SCCs - run non-root and drop capabilities
  • Use ImageStreams + DeploymentConfigs/Deployments for rollouts
  • Adopt app-of-apps to manage many Applications declaratively
  • Enable selfHeal + prune so the cluster always matches Git

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 Argo CD 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