The last stop in this year's Kyma journey lands in Armenia to visit Yerevan, one of the oldest cities in the world. Yerevan is called the "pink city" due to the color of the stone used for building. Staying in the same tone, we put on the rose-colored glasses and look forward to the future releases that are to come in 2021. For the time being, read about the changes introduced in 1.18 that focus mostly on CLI, Monitoring, Kiali, and Console.
CAUTION: Read the Migration Guide before upgrading your Kyma deployment to 1.18.
See the overview of all changes in this release:
- CLI - Consistent flag names across all commands, changes to the installation command, more intuitive AKS provisioning command
- Monitoring - Full upgrade of all monitoring components
- Kiali - Kiali Operator removed
- Console - Baked-in docs removed from the Console UI
- Known issues - Prometheus-Istio crashes
In this release, we fixed the inconsistency in the naming of CLI command flags. Here is the complete list of changes:
kyma provision minikubecommand
For more information about the possible commands, flags, and options, read Kyma CLI documentation.
In 1.18, the
--source=latest option in the
kyma install command was changed to
--source=master. The previous option name gave users the wrong idea that the command installed the latest Kyma release version instead of the latest revision from the
Furthermore, we removed the
--source=latest-published option and integrated this functionality with the
--source=master option. If the artifacts for the latest revision are not available on the
master branch yet, you will be asked to confirm if you want to use the previous revision.
kyma provision aks command now expects a JSON file for specifying the Azure Service Principal instead of a TOML file which turned out to be an error-prone and uncommon format.
All monitoring components got upgraded to the latest versions.
To reduce the maintenance efforts and resource consumption, we removed the Kiali Operator and now we just bundle the plain Kiali deployment with Kyma. See issue #9866 for reference.
As some of you might have already noticed, Rafter has recently entered the maintenance mode. It has served us for a long time as a backend mechanism for storing API specifications, Service Class-related documentation, and baked-in documentation in the Console UI. Since we are planning to replace Rafter's functionality with a different solution, we are moving slowly but surely away from it. As the first step, we have decided to remove the baked-in documentation that you could access in the top-right corner of the Console UI under the question mark icon. This way, we reduced the footprint of the runtime and made it more lightweight. Worry not as the docs are still available on our website in all of their shapes and forms.
As for Rafter, if you are interested in adopting it (and adapting to your liking), it is still looking for some caring foster parents.
With the switch to Istio telemetry v2 (required for Istio 1.7), an important feature of metric retention is still missing in the Istio-proxy. Due to that, under heavy service topology changes, there might be proxy instances such as ORY Oathkeeper that keep orphaned metrics scraped by the Prometheus-Istio instance. This can cause an OOM crash. See issue #9867 to learn more.