Home > Workload Solutions > Container Platforms > Red Hat OpenShift Container Platform > Archive > Implementation Guide—Red Hat OpenShift Container Platform 4.10 on AMD-powered Dell Infrastructure > Installing OpenShift using Zero-Touch Provisioning
You can use Zero-Touch Provisioning (ZTP) to deploy OpenShift Container Platform in a hub-spoke architecture, where a single hub cluster can manage multiple spoke clusters in a disconnected environment. For more information, see Red Hat ZTP documentation.
Prerequisites
To use ZTP, you need:
CSAH nodes host the RHCOS ISO and RootFS images that will be used to provision the distributed unit bare-metal hosts.
[core@csah-pri ~]$ export ISO_IMAGE_NAME=rhcos-4.10.16-x86_64-live.x86_64.iso
[core@csah-pri ~]$ export ROOTFS_IMAGE_NAME=rhcos-4.10.16-x86_64-live-rootfs.x86_64.img
[core@csah-pri ~]$ export OCP_VERSION=4.10.16
[core@csah-pri ~]$ sudo wget https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/4.10/${OCP_VERSION}/${ISO_IMAGE_NAME} -O /var/www/html/${ISO_IMAGE_NAME}
[core@csah-pri ~]$ sudo wget https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/4.10/${OCP_VERSION}/${ROOTFS_IMAGE_NAME} -O /var/www/html/${ROOTFS_IMAGE_NAME}
At a high level, preparing the hub cluster includes:
The assisted installer service deploys OpenShift Container Platform clusters. Create an instance of AgentServiceConfig CR by using this sample YAML file and updating the required parameters:
[core@csah-pri ~]$ oc apply -f <agentServiceConfig.yaml>
Note: This implementation guide uses automated CR creation: the Automated SiteConfig method is used to install the spoke cluster.
To configure the hub cluster:
Figure 14. OpenShift GitOps operator installation
Figure 15. TALM operator installation
i Export the argocd directory from the ztp-site-generate container image by running the following commands:
[core@csah-pri ~]$ mkdir gitops
[core@csah-pri ~]$ cd gitops
[core@csah-pri gitops]$ podman pull registry.redhat.io/openshift4/ztp-site-generate-rhel8:v4.10
Note: If the pull command fails, verify that you are logged in using the podman login registry.redhat.io command and Red Hat credentials.
[core@csah-pri gitops]$ mkdir -p ./out
[core@csah-pri gitops]$ podman run --log-driver=none --rm registry.redhat.io/openshift4/ztp-site-generate-rhel8:v4.10 extract /home/ztp --tar | tar x -C ./out
ii Create a directory structure with separate paths for the SiteConfig and PolicyGenTemplate custom resources (CRs) in your GitHub repository by following the structure in the out/argocd/example directory. See the Red Hat document Preparing ZTP Git repo.
i In the OpenShift console, click the Bento menu icon in the upperupper right corner and select Cluster Argo CD. Log in using your OpenShift credentials.
ii Under Settings, configure access to the repository:
Figure 16. Argo CD settings
Repositories: Add the connection information and credentials. The URL must end in .git—for example, https://github.com/dell-esg/openshift-bare-metal.git.
Certificates: Add the public certificate for the repository, if needed.
If needed, update the out/argocd/deployment/policies-app.yaml.
[core@csah-pri gitops]$ oc patch argocd openshift-gitops \
-n openshift-gitops --type=merge \
--patch-file out/argocd/deployment/argocd-openshift-gitops-patch.json
[core@csah-pri gitops]$ oc apply -k out/argocd/deployment
To deploy a spoke cluster:
Figure 17. Host Inventory
Figure 18. Downloading discovery ISO
Figure 19. Approving host to join cluster
Figure 20. Monitoring the cluster status
The kubeadmin user credentials and the kubeconfig file are available on the ACM portal.