Loading...

XML

Word

Printable

Workaround:

Workaround Exists
Workaround Description:

Hide

Apply 0.6.0 imagestreams: https://raw.githubusercontent.com/kiegroup/kogito-cloud/0.6.0/s2i/kogito-imagestream.yaml

Show
Apply 0.6.0 imagestreams: https://raw.githubusercontent.com/kiegroup/kogito-cloud/0.6.0/s2i/kogito-imagestream.yaml
Steps to Reproduce:
Hide

Used CR:

apiVersion: app.kiegroup.org/v1alpha1 kind: KogitoApp metadata: name: hr-service spec: build: gitSource: uri: https://github.com/kiegroup/kogito-examples contextDir: onboarding-example/hr imageRuntime: imageStreamTag: 0.5.1 imageS2I: imageStreamTag: 0.5.1 service: labels: department: process id: process employeeValidation: process

Apply imagestreams for 0.5.1 and apply this CR.

Then update the CR with 0.6.0 version to runtime and s2i tags and apply the CR.
No 0.6.0 imagestreamtags are created.
Show
Used CR: apiVersion: app.kiegroup.org/v 1 alpha 1 kind: KogitoApp metadata: name: hr-service spec: build: gitSource: uri: https://github.com/kiegroup/kogito-examples contextDir: onboarding-example/hr imageRuntime: imageStreamTag: 0 . 5 . 1 imageS 2 I: imageStreamTag: 0 . 5 . 1 service: labels: department: process id: process employeeValidation: process Apply imagestreams for 0.5.1 and apply this CR. Then update the CR with 0.6.0 version to runtime and s2i tags and apply the CR. No 0.6.0 imagestreamtags are created.

The Operator does not create the specific imagestreamtag if the imagestream is already present in the namespace or openshift namespace.

blocks

KOGITO-692 Operator allow to define different versions in KogitoApp CR but does not allow them to be different when executing

is caused by

KOGITO-160 Add capability to create Kogito image streams in case they are missing