Edgar Hernandez
May 2 · 5 min read

Sprint #21 has just finished and there are, not one, not two, but three new releases ❕❗❕ ️ I blame the agile development approach ;)

There was a mid-sprint v0.18.0 release to make available the new Kiali operator. Also, there was a v0.18.1 patch release, because of an issue with Kubernetes clusters. Finally, the traditional end-of-sprint release is v0.19.0.

Ok, let’s talk about the new stuff…

If you like to watch, this is the recording of this Sprint’s demo is available in Kiali’s YouTube channel:

If you prefer a written update, read on to see an overview of this Sprint feature updates!

Migration to PatternFly 4

Kiali was using PatternFly 3 as the base for visual appearance. This sprint PatternFly library was upgraded to version 4 and now Kiali looks a bit different:

If you are trying Kiali 0.19, please report us any inconsistency or issue you find in the front-end. Although a good effort was done to upgrade to PatternFly 4, some controls may be missed and visuals may not be on par with the rest of the UI.

Runtime metrics discovery

Kiali previously required a kiali.io/runtime annotation on pods where was desired to enable and show runtime dashboards.

The runtime dashboards feature has been improved and the mentioned pod annotation is no longer required. Kiali will try to resolve the runtime from available metrics and automatically enable runtime dashboards as needed.

For more info, read the documentation in our website.

Support for updating Traffic routing in Wizards

In past sprint updates, the Traffic routing wizards have already been demoed and discussed. Currently, there are three wizards available to create: weighted routing, matching routing and traffic suspension.

The wizards only allowed you to create routing rules. Once created, changes were done in the YAML editor. Alternatively, you could delete and use the wizards to re-create the traffic rules.

In this sprint, support to update routing configurations through the wizards has been included. After setting the configs, the actions menu will show options like in this image:

Naturally, the wizard that will be enabled for editing, will be the one you used to initially create the routing.

Kiali operator

The operator is the new way of installing Kiali and the preferred one. The operator was made available when the extraordinary v0.18 release was published — and, as previously commented, the operator is the culprit of the extraordinary release ;)

The Kiali website has been updated with instructions to install Kiali using the operator. Also, the Readme.md file of the repository has been updated.

If you install Kiali using Istio’s Helm charts or the demo profile, Kiali will be installed via the old method. Make sure to clean your environment if you later choose to use the operator.

Workload logs

In the details page of Workloads, there is a new Logs tab. As its name suggests, this tab will let you view the logs of a Workload.

Remember that under Istio’s definition, a Workload is not equivalent to a Pod. A Workload can encompass more than one Pod. This is the reason why you will be able to choose which Pod you want to see its logs and, then, a container from within the Pod.

Links from traffic tab

As a usability improvement, links to detailed metrics pages were added to the Traffic tab:

On rows listing apps (any direction) and services (outbound direction), clicking View metrics will direct you to the Inbound or Outbound metrics tabs (depending on your selection) and filters will be pre-selected to show details of the chosen connection.

On rows showing workloads (any direction) and services (inbound direction) Kiali doesn’t have enough filters to show detailed metrics for these connections, so you will be directed to unfiltered detailed metrics.

Available filters for Inbound Metrics

In the image at the left, you can see that the “Remote service” option is missing. Also, there is no “Remote workload” option in neither metrics tab. These are the missing filters to get consistent behavior for all “View metrics” links.

It would be nice if you contribute to add the missing filters 😉

Validate ports for services and deployments

When you deploy your app and mistakenly specify different ports in the Service and Deployment resources, the Pods may not become available. The Service list will now inform about this condition and show an error:

Kiali images are also on Quay.io

Quay is an application and container registry. It’s an alternative to DockerHub. Kiali images are being published both to DockerHub and Quay; use the registry you like better. Operator images are only being pushed to Quay.

Stay in touch!

Remember that Kiali is on GitHub and you can see the list of all Kiali back-end and Kiali front-end changes for Sprint #21.

If you haven’t used Kiali, give it a try and tell us if you like it! Check out the Getting started guide available in our website.

Don’t forget to follow us on Twitter.


Service Mesh Observability

Thanks to Alissa Bonas

Edgar Hernandez

Written by



Service Mesh Observability

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade