It’s been seven+ years and Istio Service Mesh is still on the rise. And for nearly as long the Kiali project has been developed alongside, to supply

Kiali 2.0 for Istio. It’s been seven+ years and Istio… | by Jay Shaughnessy | Kiali | Oct, 2024 | Medium

submited by

Style Pass

2024-10-22 10:00:06

It’s been seven+ years and Istio Service Mesh is still on the rise. And for nearly as long the Kiali project has been developed alongside, to supply a world class console for Istio. Istio continues to evolve and so we’ve decided that now is the right time, with Istio Ambient emerging, to make a major version change. So, let me introduce a few key changes for Kiali 2.0.

If you have configured Kiali then you are likely aware of our fairly complex way of defining “Accessible Namespaces”. The set of namespaces that Kiali knows about and can present to the user, is currently the result of all of these settings:

Getting it right, including things like regex expressions, could be daunting. In Kiali 2.0 they have all been retired in favor of the same mechanism used by Istio to limit namespace scope: Discovery Selectors. And by the way, if you don’t use these in Istio then you may want to, it can narrow what the control plane has to do. In short, these are Kubernetes Label Selectors that define the set of namespaces, based on labels, that Kiali will care about.

NOTE: If you have customized Kiali’s accessible namespaces in 1.x, then this is a breaking change and you will need to update configuration when updating to Kiali 2.x.