Home > Workload Solutions > Container Platforms > Red Hat OpenShift Container Platform > Guides > Implementation Guide—Red Hat OpenShift Container Platform 4.14 on AMD-powered Dell Infrastructure > Agent-based installer cluster deployment
The agent-based installer can run offline and is useful for clusters that are in a restricted network without Internet access.
The Mirror Registry for Red Hat OpenShift is designed for initial cluster deployment when no other registry is available for use. Dell Technologies recommends a highly available setup for the OpenShift mirror registry, such as Red Hat Quay. The following section of this guide describes the process for mirroring only the OpenShift Container Platform image repository that is needed for the initial cluster deployment and not designed to be the ongoing registry in a production environment. For information about mirroring the custom catalogs that are required for operator installation, see Mirroring images for a disconnected installation.
Note: A mirror registry is required for disconnected installations. Various options are available for the mirror registry, including Red Hat Quay, JFrog Artifactory, and Harbor. For more information, see About disconnected installation mirroring. The container images must be mirrored before you start the deployment.
Ensure that:
To install a mirror registry for the OpenShift cluster:
tar -xvf mirror-registry.tar.gz
./mirror-registry install --quayHostname <fqdn of the mirror registry host> --quayRoot <installation directory>
Use an absolute path for quayRoot when running the mirror registry script.
Note: Make a note of the init user credentials in the output of the preceding command. These credentials are required for access to the mirror registry CLI and UI.
podman login -u init -p <password> https://<fqdn of the mirror registry host>:8443
Note: If there is a certificate issue, copy the rootCA.pem that is in the <installation directory>/quay-rootCA folder to /etc/pki/ca-trust/source/anchors and run the update-ca-trust command to update the certificates.
https://<fqdn of the mirror registry host>:8443
cat ./pull-secret | jq . > <path>/<pull_secret_file_in_json>
echo -n '<user_name>:<password>' | base64 -w0
"auths": {
"<mirror_registry>": {
"auth": "<credentials in base64 format generated in previous step>",
"email": "<email id>"
}
}
Ensure that the mirror registry host has Internet access, and then perform the following steps:
#Export the release version, change the version as required:
OCP_RELEASE=4.14.0
#Export the local registry name and host port:
LOCAL_REGISTRY='<fqdn of the mirror registry host>:8443'
#Export the local repository name:
LOCAL_REPOSITORY='ocp4/openshift414'
#Export the name of the repository to mirror:
PRODUCT_REPO='openshift-release-dev'
#Export the path to your registry pull secret:
LOCAL_SECRET_JSON='<path to pullsecret file in json format>'
#Export the release mirror:
RELEASE_NAME="ocp-release"
#Export the type of architecture for your server:
ARCHITECTURE=x86_64
oc adm release mirror -a ${LOCAL_SECRET_JSON} --from=quay.io/${PRODUCT_REPO}/${RELEASE_NAME}:${OCP_RELEASE}-${ARCHITECTURE} --to=${LOCAL_REGISTRY}/${LOCAL_REPOSITORY} --to-release-image=${LOCAL_REGISTRY}/${LOCAL_REPOSITORY}:${OCP_RELEASE}-${ARCHITECTURE}
This command retrieves the release information as a digest. The information about mirrors is unique to the mirrored repository.
The command output includes the imageContentSources data that is required during the cluster installation. Note down the imageContentSources data to add to the install-config.yaml file during the cluster installation. The following code excerpt is from the imageContentSources section:
imageContentSources:
- mirrors:
- csah.dcws.lab:8443/ocp4/openshift414
source: quay.io/openshift-release-dev/ocp-release
- mirrors:
- csah.dcws.lab:8443/ocp4/openshift414
source: quay.io/openshift-release-dev/ocp-v4.0-art-dev
The CSAH node is used to run the installer.
To start the deployment:
https://mirror.openshift.com/pub/openshift-v4/x86_64/clients/ocp/stable/openshift-install-linux.tar.gz
The images version that is already downloaded in the mirror registry must match that version. For example, if you want to deploy a cluster on version 4.14.0, ensure that you have downloaded the 4.14.0 images into the mirror registry.
wget https://mirror.openshift.com/pub/openshift-v4/x86_64/clients/ocp/4.14.0/openshift-install-linux.tar.gz
tar -xzvf openshift-install-linux.tar.gz
cp openshift-install /usr/local/bin
sudo dnf install /usr/bin/nmstatectl -y
mkdir ~/dir-install
Note: Ensure that the file names are install-config.yaml and agent-config.yaml and that the files are present in the installation directory.
tr -d '[:space:]' < <pull scret file in json format>
openshift-install --dir dir-install/ agent create image
openshift-install --dir dir-install/ agent wait-for bootstrap-complete --log-level=debug
The following figure shows the command output:
openshift-install --dir dir-install agent wait-for install-complete
The following figure shows the command output from a successful installation: