kiali: Istio config bug
Bug brief
I’m testing Istio with gateway API and httproutes. It’s all accessible and working well. But in Kiali saying as below img.
If I put full name like dev-grafana.monitoring.svc.cluster.local, Istio config is fine but can’t route to the App anymore.
Environment
Currently I’m running
- Kiali version: v1.78.0
- Istio version: 1.20.0
- Kubernetes version: 1.26
- Other notable environmental factors: Gateway API, HTTPROUTES
About this issue
- Original URL
- State: closed
- Created 7 months ago
- Comments: 15 (6 by maintainers)
I was able to reproduce and fix the second part of the issue, when Kiali accepts FQDN as a Service name. But the initial issue when Service ‘kiali’ set as a service name is showing error I cannot reproduce:
@Zorgji I mean the issue is fixed partially, and the fix will be available on upcoming Kiali v1.79 in 6 weeks. However the error message when you set
kialiordev-grafanaas a service name, I was not able to reproduce on my environment with Istio 1.20 and Kiali 1.78 or latest, it appears only in the case when I set theistio_identity_domain:in Kiali configmap with emptysvc.cluster.local. BTW the validation errors can be ignored by setting property in Kiali configmap:Thank you @Zorgji, you are right, the issue is in validations. I will make a fix.
@hhovsepy Perhaps the validation here is too aggressive?