Adding images to an external registry

To add build images for Maximo® Manage to an external registry, configure the custom resource for the Maximo Manage workspace.

Before you begin

Before you can configure Maximo Manage to store build images in an external registry, you must create a secret that is based on Docker credentials for the external registry repository.

  1. Log in to the Red Hat® OpenShift® console.
  2. In the workspace where the Maximo Manage custom resource is located, use the command line interface or the Red Hat OpenShift dashboard to create an image pull secret.
    For example, you can use the command line interface to create the secret:
    kubectl create secret docker-registry regcred 
--docker-server=your_docker_registry_server 
--docker-username=your_your_docker_registry_account 
--docker-password=your_your_docker_registry_api_key

About this task

When Maximo Manage is deployed or updated, the build process generates an administrative image and a server bundle image for each bundle type. Bundle types are specified in the custom resource for the workspace. Images are stored in an internal registry.

Sometimes, you might want to store the build images in an external repository. For example, you might want to run security scans on images that have customizations, or you might want to test builds independently before you deploy the application in Maximo Application Suite. Administrators can configure Maximo Manage to store images in an external repository.

To configure Maximo Manage to add build images to an external registry, you must add the registryForGeneratedImages properties to the spec.settings section of the custom resource and specify values for the following fields:
registryPath
The path to the repository where you want to store the image.
secretName
The secret that contains the credentials for accessing the repository.

Procedure

  1. In the Red Hat OpenShift console, from the side navigation menu, click Administration > Custom Resource Definitions.
  2. Open the Maximo Manage workspace and then on the Instances tab, click the instance for your external registry.
  3. On the YAML tab in the spec.settings section, add the following lines: 
    registryForGeneratedImages:
	          registryPath:
	          secretName:
  4. Specify values for the registryPath and secretName fields, as shown in the following example: 
    spec:
  settings:
    ...
    languages:
	  baseLang:
	  secondaryLangs:
    registryForGeneratedImages:
	  registryPath: your_docker_registry_server
	  secretName: your-image-pull-secret-for-the-repository
  5. Save the custom resource.

Results

The Maximo Manage workspace operator automatically picks up the change to the custom resource. A build is started, and the new images are pushed to the external registry. You can use the images to deploy Maximo Manage on a local computer.

If you no longer want to push build images to an external repository, remove the lines of code that you added for the external registry from the custom resource for the workspace.