Manual setup of the base image ImageStreams

Note: This step is not necessary if the image mirroring for ImageStreams is working properly in your cluster. For IBM Cloud OpenShift Clusters this step is required.

In case the image mirroring is not working for ImageStreams in your cluster please perform the following workaround:

  • Please open the ImageStreams overview in your installation namespace (e.g. k5-tools) in the OpenShift Console

    • Navigate to Builds → ImageStreams

  • Disable automated creation of the ImageStreams (after the IBM Industry Solutions Workbench Operator has reconciled the three Imagestreams will be deleted: k5-domain-server, k5-solution-ubi8-node, k5-solution-ubi8-openjdk)

    • add the following value spec.values.service-builder.k5-pipeline-manager.tekton.imageStreams.initialize: false to your ISW Custom Resource, like:

apiVersion: k5.ibm.com/v1beta1
kind: ISW
metadata:
  name: k5-tools
  namespace: k5-tools
spec:
  designer:
    enabled: true
  domain: apps.openshift.my.cloud
  license:
    accept: true
  values:
    global:
      network:
        egressPolicy:
          enabled: false
    service-builder:
      k5-pipeline-manager:
        tekton:
          imageStreams:
            initialize: false

  • Please open the default ServiceAccount in your installation namespace (e.g. k5-tools) in the OpenShift Console and add the image pull secret (ibm-entitlement-key)

    • Navigate to User Management → ServiceAccounts

    • Open the ServiceAccount default

    • Add an entry with name ibm-entitlement-key to the imagePullSecrets section

    • The default ServiceAccount should look like the following example (please do not change or delete the ServiceAccount, only add the image pull secret):

kind: ServiceAccount
apiVersion: v1
metadata:
  name: default
  namespace: k5-tools
secrets:
  - name: default-token-69fdc
  - name: default-dockercfg-tm9ch
imagePullSecrets:
  - name: default-dockercfg-tm9ch
  - name: ibm-entitlement-key

  • Apply the following ImageStreams manually to your installation namespace, e.g. k5-tools (Note that the name, tag, image name and image digest must not be changed, only the <YOUR_PRIVATE_REGISTRY> placeholder should be replaced with your registry)

kind: ImageStream
apiVersion: image.openshift.io/v1
metadata:
  name: k5-domain-server
  namespace: k5-tools
spec:
  lookupPolicy:
    local: false
  tags:
    - name: 6.0.96
      from:
        kind: DockerImage
        name: <YOUR_PRIVATE_REGISTRY>/isw_release-domain-server@sha256:d9a592df5263f26b5da973fcc42a21f846abd847c7006c8a73cce46351f19593
      importPolicy:
        importMode: Legacy
      referencePolicy:
        type: Source
kind: ImageStream
apiVersion: image.openshift.io/v1
metadata:
  name: k5-solution-ubi8-node
  namespace: k5-tools
spec:
  lookupPolicy:
    local: false
  tags:
    - name: 5.2.14
      from:
        kind: DockerImage
        name: <YOUR_PRIVATE_REGISTRY>/isw_release-solution-ubi8-node@sha256:733f78296fbf371e5ece203945a11ea9a9a30352562c3cb73458202de9de4d60
      importPolicy:
        importMode: Legacy
      referencePolicy:
        type: Source
kind: ImageStream
apiVersion: image.openshift.io/v1
metadata:
  name: k5-solution-ubi8-openjdk
  namespace: k5-tools
spec:
  lookupPolicy:
    local: false
  tags:
    - name: 5.2.14
      from:
        kind: DockerImage
        name: <YOUR_PRIVATE_REGISTRY>/isw_release-solution-ubi8-openjdk@sha256:058e495d661a934b7a5d294d0a1a5216ea37e72660710f610644da00cc9f5b34
      importPolicy:
        importMode: Legacy
      referencePolicy:
        type: Source
Note: You can also use the automatically created base ImageStreams as templates and only replace the value de.icr.io/isw_release with your registry.

  • Open and validate the created ImageStreams (no error should be shown)