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 BuildsImageStreams

  • 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 ManagementServiceAccounts

    • 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: 7.0.79
      from:
        kind: DockerImage
        name: <YOUR_PRIVATE_REGISTRY>/isw_release-domain-server@sha256:dd1ef97df3c228c71dcf192064a949813f74edfd756b3f384a50d03dea20ed30
      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: 10.0.48
      from:
        kind: DockerImage
        name: <YOUR_PRIVATE_REGISTRY>/isw_release-solution-ubi8-node@sha256:f8ab83fc68236c724fb059c5f5a744933e341931920409f005f4d3e5a663f49c
      importPolicy:
        importMode: Legacy
      referencePolicy:
        type: Source
kind: ImageStream
apiVersion: image.openshift.io/v1
metadata:
  name: k5-solution-ubi8-openjdk-11
  namespace: k5-tools
spec:
  lookupPolicy:
    local: false
  tags:
    - name: 10.0.48
      from:
        kind: DockerImage
        name: <YOUR_PRIVATE_REGISTRY>/isw_release-solution-ubi8-openjdk-11@sha256:abaed2668e9e429b48008e31138cb64e8db8c786b3a64ead61d3e6b293964984
      importPolicy:
        importMode: Legacy
      referencePolicy:
        type: Source
kind: ImageStream
apiVersion: image.openshift.io/v1
metadata:
  name: k5-solution-ubi8-openjdk-17
  namespace: k5-tools
spec:
  lookupPolicy:
    local: false
  tags:
    - name: 10.0.48
      from:
        kind: DockerImage
        name: <YOUR_PRIVATE_REGISTRY>/isw_release-solution-ubi8-openjdk-17@sha256:8ec03c3766e272ca9d4fc0d8ad237ca9bbb12541f26ae187cd1065403868b4f2
      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)