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:
- add the following value
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 theimagePullSecrets
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:426f0d546b74d044b89de807cf034e13feac55db6cbfcda1b09790a04699d99d 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:fe8925aa80b19b138fe6c0339cd1a65aa491c3725e70f43d5e1df1cf0b9db9e3 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:b3646a5bc0c26737499555f0e6544430c75b488b1eb55b16d63b1b606e66c655 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:aae0ce27ed5381fbe946e86fddf7ef5fc7a07c01737b3d6b32f6b805685d9656 importPolicy: importMode: Legacy referencePolicy: type: Source
kind: ImageStream apiVersion: image.openshift.io/v1 metadata: name: k5-solution-ubi8-openjdk-17-ppc64le 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-ppc64le@sha256:51aff300c2e49320e891792fad044f9ca3cc5881ec7e1043e54354d5989ece47 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)