-
Task
-
Resolution: Unresolved
-
Minor
-
maistra-1.1.0
-
None
-
None
There is a following kiali part in SM CR:
kiali: enabled: true hub: quay.io/kiali-qe image: kiali tag: corev1.12uiv1.12
The deployment part of kiali CR looks like this:
deployment: image_name: quay.io/kiali-qe/kiali image_pull_policy: Always ingress_enabled: true namespace: istio-system
In case of SM 1.0:
SM 1.0 CR:
kiali: enabled: true hub: quay.io/kiali-qe image: kiali tag: corev1.0uiv1.0
kiali CR:
deployment: image_name: quay.io/kiali-qe/kiali image_pull_policy: Always image_version: corev1.0uiv1.0 ingress_enabled: true namespace: istio-system version_label: corev1.0uiv1.0
So in case of SM 1.1 the 'image_version' and 'version_label' parameters in kiali CR are not created.
We use custom images for kiali testing and this issue is causing kiali deployment failures.
Current workaround is to patch the kiali CR after installation to add 'image_version' parameter.
- is related to
-
MAISTRA-1256 SM Operator Not Creating 'version' In Kiali CR
- Closed