use kiali 1.4 so it can pick up patches

[linsun]

Based on recommendation from kiali team and what we have done in 1.2.

[ ] Configuration Infrastructure
[ ] Docs
[x ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

[howardjohn]

i think using a pinned version is a better idea but given that 1) we clearly aren't good at keeping it update to date and 2) we had it this way before, this seems fine. Thanks!

[jmazzitelli]

Yes, using just vX.Y (as opposed to vX.Y.Z) is how we've been doing it since Istio 1.1 and 1.2:

https://github.com/istio/istio/blob/release-1.1/install/kubernetes/helm/istio/charts/kiali/values.yaml#L7
https://github.com/istio/istio/blob/release-1.2/install/kubernetes/helm/istio/charts/kiali/values.yaml#L7

[istio-testing]

@linsun: The following test failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
pilot-multicluster-e2e_istio	751aa41	link	/test pilot-multicluster-e2e_istio

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[clyang82]

i think using a pinned version is a better idea but given that 1) we clearly aren't good at keeping it update to date and 2) we had it this way before, this seems fine. Thanks!

I think using a pinned version may leads the version we are testing in the release is different from the version user is using. That may have bug that we cannot cover in our release. Anyway, I think we should switch to kiali operator to leverage the kiali's experts for that.