Sprint #25 has ended and, with it, the new Kiali v1.2.0 release is out. This is yet another short update :-)
First, I would like to say “thank you” to the community for the interest on Kiali. We’ve noted an increased amount of people making contact to ask questions, propose features, report issues and to also make code contributions.
This sprint, there was a good effort improving the operator and making it robust. To be honest, since the operator improvements are usually not visible at all, this post doesn’t do justice to that effort (and neither the demo video). Something worth to mention is that the OperatorHub was updated to include version 1.1.0 of the Kiali operator (which was the latest one at that moment). The next plan regarding the Kiali operator is to add Phase II capabilities.
Anyway, let’s go with the visible new features. If you like to watch, here the demo of Sprint #25 available in Kiali’s YouTube channel:
For people who like to read, just continue reading.
Generate YAML to install operator
In the getting started guide, it’s stated that you should use the following command to install the operator:
bash <(curl -L https://git.io/getLatestKialiOperator)
--dry-run parameter was added to let you run the script like:
bash <(curl -L https://git.io/getLatestKialiOperator) \
Instead of installing the operator in your cluster, the script will write a YAML file that you can pass to
kubectl apply to install the operator.
Support for pull secrets in the Kiali operator’s CR
If you are using private registries for your container images, you need Secrets to pull images from these private registries and configure the pods accordingly.
Support for image pull secrets was added to the Kiali operator to allow using private registries without further changes to the Kiali deployment.
# The names of the secrets to be used when container images are to be pulled.
# image_pull_secrets: 
# Determines which version of Kiali to install.
# Choose "lastrelease" to use the last Kiali release.
Using UBI-minimal as base container image
On Kiali v0.21 we moved from using CentOS7 to using Red Hat Universal Base Image 7 as the base image for building Kiali’s container image. The motivation of the move was to use a base image with vulnerability fixes (based on the security scans that Quay.io and DockerHub have available).
Kiali container image has been increasing its size over the time and it was about ~129MB for v1.1.0. Fortunately, there is a minimal version of the Red Hat Universal Base Image, and using it generates a Kiali image of about ~84MB. That’s about ~34% smaller! And the switch was trivial. So, Kiali is now using the minimal image to benefit from smaller builds.
Non-traffic TCP edges
Perhaps at some point you have seen gray edges in the Kiali graph. These edges are indicating that there is no traffic for the selected timespan, but the same arrow head was being used regardless whether past traffic was HTTP or TCP. This was improved and the arrow head will make distinction of the past traffic type:
Web page improvements
A new Frequenty Asked Questions section has been added to the web page.
This new section aims to answer some common issues as well as common questions we’ve receiving through GitHub.
The Validations section is also updated to contain all current documentation about checks being run by Kiali on Istio resources.
In general, the web page is receiving a good amount of updates to ensure that the content is current. There is also an ongoing re-design effort to make it look better. Expect the new look soon!
Stay in touch!
That’s the update of this sprint. Remember that this post is presenting the most relevant features, and complementing the recorded demo. You can see the full list of changes in GitHub, in the Kiali back-end and Kiali front-end repositories.
If you haven’t used Kiali, give it a try! Check out the Getting started guide available in our website.
Don’t forget to follow us on Twitter.