- OpenShift cluster (4.12+),
ocCLI, cluster admin privileges
oc cluster-info
oc whoamioc apply -k clusters/global/
./bin/monitor-status applications.argoproj.ioThis single command creates all ArgoCD applications with proper ordering:
- Wave -1: OpenShift GitOps (self-management)
- Wave 1: Pipelines (Tekton operator)
- Wave 2: Vault (secret management)
- Wave 2: ESO (External Secrets Operator)
- Wave 3: ACM (Advanced Cluster Management with ordered deployment)
- Operator → Hub → Policies
- Wave 4: GitOps Integration (cluster import)
- Wave 5: Hub Provisioner Pipelines
./bin/wait-kube route openshift-gitops-server openshift-gitops '{.metadata.name}' openshift-gitops-server
./bin/wait-kube mch multiclusterhub open-cluster-management '{.status.conditions[?(@.type=="Complete")].message}' "All hub components ready."oc get applications -n openshift-gitops # All "Synced" and "Healthy"
oc get multiclusterhub -n open-cluster-management
oc get pods -n vault./bin/bootstrap-vaultecho "OpenShift: $(oc whoami --show-console)"
echo "ArgoCD: https://$(oc get route openshift-gitops-server -n openshift-gitops -o jsonpath='{.spec.host}')"
echo "ACM: https://$(oc get route multicloud-console -n open-cluster-management -o jsonpath='{.spec.host}')"- GitOps Installation: ArgoCD operator installs and configures itself
- Ordered Application Deployment: Sync waves ensure proper dependency order
- GitOps Setup: ArgoCD ApplicationSets configured for cluster management
- Secret Management: Vault and ESO configured for secure credential handling
- Multi-Cluster Ready: ACM hub ready to manage regional clusters
After bootstrap completes:
# Add your first cluster
./bin/cluster-create
# Monitor cluster provisioning
oc get clusterdeployments -A # OpenShift clusters
oc get clusters -A # EKS clusters
# Check overall health
./bin/monitor-healthThe cluster is now ready to provision and manage additional regional clusters through GitOps automation.