Istio Component Status: providing better insight

[Xavier Canal Masjuan]

Hello there,

Kiali has the Istio Component Status feature which aims to warn mesh users in case the mesh is not healthy.

 

The status of each component is basically based on its deployments: if the deployment is found, then does the cluster have the desired replicas available? If not, it is considered as not healthy. If the deployment is not found, then kiali shows it as Not Found.

However, there is an issue[1] where it bolds that add-ons like Prometheus are not necessarily deployed with deployments.

The question is, what would be useful for you to highlight in that feature? Is it the desired replica matching in each deployment? Perhaps, highlight if kiali reaches those services (status: service unreachable)? What do you do to check that the control plane is running and fully working?

Feel free to answer in here or join the conversation in the commented issue[1].

Thank you very much,

[1] https://github.com/kiali/kiali/issues/3353

--

Xavier Canal i Masjuan

[Edgar Hernández]

Hi, Xavier.

IMHO, as Istio is treating "other" components as simple add-ons, I think the best route right now is to somehow "ping" prometheus/jaeger.
I even think that people can choose to run prometheus/jaeger outside of Kubernetes, so you will have nothing but a bare URL to try to make contact.

That's my 2 cents.

--
You received this message because you are subscribed to the Google Groups "kiali-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kiali-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kiali-users/CAMdCR0MSUXRkutuXJdEZPNdaccPrvUUS1hZVXpp9_i264YaNcw%40mail.gmail.com.