https://www.openshift.com/learn/topics/gitops/

Demo an example of what is possible with Red Hat Advanced Cluster Management(ACM) running on OpenShift configuring other OpenShift clusters and xKS clusters. Use Tools like Crossplane to provision xKS clusters with ACM. Use CertManager to issue certificates with LetsEncrypt.

Zero touch provisioning (ZTP) is a technique that allows to provision new edge sites with declarative configurations of bare-metal equipment at remote sites.

Sample applications for OpenShift GitOps in a homelab

Installation of RHACM and Openshift-Gitops. Deployment of Helm-based RHACM applications with external values files or kustomize.

Use Openshift GitOps(ArgoCD) to build Applications

OpenShift Gitops installation script.

Coffeeshop app infrastructure (HELM chart deployed via ArgoCD)

This workshop aims to introduce participants to the world of GitOps and its applications in continuous integration and continuous deployment (CI/CD) on OpenShift using Tekton pipelines and Quay.

This repo is a Git-driven factory for building ROSA HCP clusters with Terraform and configuring them with OpenShift GitOps. Terraform creates the cluster and bootstraps GitOps, while GitOps manages platform and workload modules through per-cluster YAML inputs. It is designed to be reusable, and easy to extend for new modules and environments.

Factory repo for deploying and managing OpenShift Dedicated (OSD) on GCP with Terraform and GitOps. Supports optional infra provisioning, existing-network/private PSC clusters, ACM registration, and bastion/CI/AAP execution patterns.

Terraform and OpenShift GitOps factory for ROSA Classic on AWS, covering optional AWS foundation build, ROSA cluster lifecycle, GitOps bootstrap, tenant onboarding, workload identity, ACM registration, storage integrations, and Day 2 platform or workload services.

Factory-style repo for building and managing Azure Red Hat OpenShift (ARO) classic clusters from Git. Terraform handles cluster creation and bootstrap, and OpenShift GitOps manages day-2 configuration. Includes reusable modules, per-cluster inputs, and CI/CD execution patterns for consistent, auditable cluster operations.