Offline (Airgap) Cluster

You have a Kubernetes or OpenShift cluster but it is a private cluster which means it does not have the internet access. Depending upon the cluster, follow the below procedures to get the installation files.

For Kubernetes Cluster

Since, your Kubernetes cluster is private and it does not have internet access, you cannot download the required installation files directly from the server. By following steps below, you can get the required files.
  1. Get an RHEL machine which has
    • internet access
    • Docker CLI (docker) or Podman CLI (podman)
    • kubectl
    • helm
  2. Download the Helm chart by following the steps mentioned in the Online installation section.
  3. Extract the downloaded helm chart.
    tar -zxf <ibm-connect-direct-helm chart-name>
  4. Get the container image detail:
    erRepo=$(grep -w "repository:" ibm-connect-direct/values.yaml |cut -d '"' -f 2)
    erTag=$(grep -w "tag:" ibm-connect-direct/values.yaml | cut -d '"' -f 2)
  5. This step is optional if you already have a docker registry running on this machine. Create a docker registry on this machine. Follow Setting up your registry server.
  6. Get the Entitled registry entitlement key by following steps a and b explained in Online Cluster under Create the entitled registry section.
  7. Get the container image downloaded in docker registry:
    docker pull $erImgTag
    Note: Skip step 8, 9 and 10, if the cluster where deployment will be performed is accessible from this machine and cluster can fetch container images from registry running on this machine.
  8. Save the container image.
    docker save -o <container image file name.tar> $erImgTag
  9. Copy/Transfer the installation files to your cluster. At this point you have both downloaded container image and helm chart for IBM Connect:Direct for UNIX. You need to transfer these two file to a machine from where you can access your cluster and its registry.
  10. After transferring the files, load the container image into your registry.
    docker load -i <container image file name.tar>

For Red Hat OpenShift Cluster

If your cluster is not connected to the internet, the deployment can be done in your cluster via connected or disconnected mirroring.

If you have a host that can access both the internet and your mirror registry, but not your cluster nodes, you can directly mirror the content from that machine. This process is referred to as connected mirroring. If you have no such host, you must mirror the images to a file system and then bring that host or removable media into your restricted environment. This process is referred to as disconnected mirroring.

Before you begin

You must complete the steps in the following sections before you begin generating mirror manifests:
Important: If you intend on installing using a private container registry, your cluster must support ImageContentSourcePolicy (ICSP).