RHACM + GitOps Bootstrap Repository

This repository bootstraps an OpenShift cluster with the following components:

• OpenShift GitOps (ArgoCD)
• Red Hat Advanced Cluster Management (RHACM)
• Governance Policies
• Extra Operators (example: cert-manager)

The repo is structured with base, overlays, and bootstrap folders to support GitOps-based cluster configuration.

---

📂 Repository Layout

.
├── base
│   ├── gitops/          # GitOps Operator, ArgoCD Instance
│   ├── rhacm/           # Advanced Cluster Management Operator + Hub
│   ├── policies/        # Example policies (with Placement + Binding)
│   └── cert-manager/    # Example extra operator (cert-manager)
│
├── overlays
│   └── dev-cluster/     # Overlay for dev cluster (includes GitOps, RHACM, Policies, Cert-Manager)
│
├── bootstrap
│   ├── 00-gitops-subscription.yaml   # Bootstrap GitOps operator
│   ├── 01-argocd-instance.yaml       # Deploy ArgoCD instance
│   ├── 02-root-applicationset.yaml   # Root ApplicationSet for GitOps, RHACM, Policies, Extras
│   ├── bootstrap.sh                  # Helper script to automate bootstrap
│   └── gitops-creds.yaml             # Git credentials for ArgoCD
│
└── README.md

---

🚀 Bootstrap Process

1. Deploy OpenShift GitOps Operator

oc apply -f bootstrap/00-gitops-subscription.yaml

Wait until the GitOps operator CSV is in Succeeded phase:

oc get csv -n openshift-operators | grep gitops

2. Deploy ArgoCD Instance

oc apply -f bootstrap/01-argocd-instance.yaml

Wait until the ArgoCD instance is available:

oc get pods -n openshift-gitops

3. Deploy the Root ApplicationSet

Once GitOps is ready, deploy the ApplicationSet that generates all ArgoCD Applications:

# Apply the ApplicationSet
oc apply -f bootstrap/02-root-applicationset.yaml -n openshift-gitops

# Verify ApplicationSet is created
oc get applicationsets -n openshift-gitops

# Check generated ArgoCD Applications
oc get applications.argoproj.io -n openshift-gitops

By default, the ApplicationSet will create the following apps for the dev-cluster overlay:

• dev-cluster-gitops
• dev-cluster-rhacm
• dev-cluster-policies
• dev-cluster-cert-manager

You can control which components are deployed by editing 02-root-applicationset.yaml.

4. Bootstrap with Script (Optional)

You can run everything with the helper script:

./bootstrap/bootstrap.sh --all

Supported options:

• --gitops-only → Deploy only GitOps
• --rhacm-only → Deploy only RHACM
• --policies-only → Deploy only Policies
• --all → Deploy GitOps, RHACM, Policies, and extras

---

🛠️ Extending with New Operators

To add a new operator (example: ServiceMesh, Logging, etc.):

1. Create a folder in base/<operator-name>
2. Add namespace.yaml, operatorgroup.yaml, subscription.yaml
3. Update 02-root-applicationset.yaml to include it as a component

---

✅ Verification

Check Application status in ArgoCD:

oc get applications.argoproj.io -n openshift-gitops

Check RHACM components:

oc get pods -n open-cluster-management

Check Policies:

oc get policies -A

Check Cert-Manager:

oc get pods -n cert-manager

---

📌 Notes

• Sync waves (argocd.argoproj.io/sync-wave) ensure proper install order:
  • GitOps → RHACM → Policies → Extras
• Policies require a ManagedClusterSetBinding and Placement to match clusters
• You can scale this pattern to multiple clusters by adding overlays