Skip to content

Load images

About this task

The Forms image must be in a container registry or repository that can be accessed by the Kubernetes or OpenShift cluster.

Before you begin

Depending on your cloud provider, there may be different types of default container image repositories already configured. Refer to the documentation of your cloud provider for setup and use of such platform container image repository.

It is assumed that you have a repository configured and running, and is reachable from all your Kubernetes or OpenShift cluster nodes. You must know the name of the repository in order to complete this task. If you are unsure what the name of the repository is, consult with your cloud provider documentation.

In the following guidance, the Docker CLI is used as a command reference. Tools like Podman may also be used, but are not described in this documentation. The procedure for the use of such tools are the same.

Authentication

If your container registry requires authentication, you must configure the Docker CLI to authenticate prior to completing the procedure. If you are uncertain if you have configured authentication you can type in the command: 

cat ~/.docker/config.json

If the docker CLI not authenticated, follow the instructions from your cloud provider to authenticate. The steps vary depending on the type of authentication used.

Retrieve Forms Container Image

The preferred method of retrieving the Forms container image is from the HCL Harbor container registry.

Load Image from HCL Harbor container registry

It is possible to pull images directly from the HCL Harbor container registry.

  1. Login to the Harbor registry. Go to your User Profile in HCL Harbor to get the CLI secret. You can copy it from the CLI secret field and you will then be asked to supply your harbor password.

    helm registry login -u <YOUR_HARBOR_USERNAME> https://hclcr.io/

  2. Retrieve the Forms charts from Harbor

    helm pull oci://hclcr.io/domino-workspace/hcl-leap-deployment --version <X.X.X>

  3. Create a kubernetes secret with the name forms-harbor with your Harbor username and CLI secret

    Note

    The values.yaml is already configured with an imagePullSecrets that points to a secret with the name of forms-harbor.

    kubectl create secret -n <YOUR_NAMESPACE> docker-registry forms-harbor --docker-server="hclcr.io" --docker-email='<YOUR_HARBOR_EMAIL>' --docker-username='<YOUR_HARBOR_USERNAME>' --docker-password='<YOUR_HARBOR_CLI_SECRET>'
    After executing the command from the previous step, you should receive the following message:

    secret/dx-harbor created

  4. Modify the yaml file to point to the Forms package on Harbor.

      images:
    pullPolicy: "IfNotPresent"
    imagePullSecrets:
      - name: "forms-harbor"
    repository: "hclcr.io"
    tags:
      leap: "9.3.13.41"
    names:
      leap: "domino-workspace/leap"

What to do next

If your container registry requires authentication, complete the topic Creating a Container Registry Secret.

Proceed to Persistent Volume Claims.

Additional Topics

Parent topic: Preparation