-
Bug
-
Resolution: Done
-
Major
-
None
-
False
-
None
-
False
-
-
---
-
---
-
-
-
2023 Week 21-23 (from May 22)
Operator is using Openshift builds to create a new workflow service, thus pushing the final image to internal registry.
But, if we set the `spec.platform.registry` information in the KogitoServerlessPlatform, the created Deployment will not use the final image from internal registry but a guessed image from specified registry.
This should be avoided or the parameter ignored when using OCP builds.
Build logs:
Pushing image image-registry.openshift-image-registry.svc:5000/kogito-workflows/greeting:0.0.1 ... Getting image source signatures Copying blob sha256:d09aca24592b99820eb623c3a56914ab82562e5a4e37aa67ece0402d832e3100 Copying blob sha256:a51869bc1fb5c30c5072f31167f78f54140a3fdd9ec65ac2ef764d86d47f30bd Copying blob sha256:06f86e50a0b74ff9eb161a7d781228877c90e8ff57e9689e8cb8b0f092a2a9f9 Copying config sha256:9b682f6fb04584a63b353268a0f761e56a3e9fa178c9309b29e77e64d8d0f7f4 Writing manifest to image destination Storing signatures Successfully pushed image-registry.openshift-image-registry.svc:5000/kogito-workflows/greeting@sha256:ba5146899b7b96ddcd5be8bc5e05c5eded34f6a1503df1d916fbe595c10e925b
Deployment definition:
$ oc get deploy greeting -o yaml apiVersion: apps/v1 kind: Deployment metadata: labels: app: greeting name: greeting namespace: kogito-workflows spec: [...] template: spec: containers: - image: quay.io/kiegroup/greeting:0.0.1
- is caused by
-
KOGITO-9106 [KSW-Operator] Add support for BuildConfig on OpenShift for limited scenarios
- Resolved
- is related to
-
KOGITO-9218 [Operator] Review Platform Conditions
- Resolved