Hoşgeldiniz! We are leaving Western Europe this month and heading to the beautiful Cappadocia in Central Turkey. This region has a very rich history beginning as early as the Bronze age. It is famous for the magical-looking Fairy Chimneys, massive rock formations caused by volcanic eruptions. In the tall vertical rocks, visitors can find houses and temples carved thousands of years ago. Today, hot-air ballooning is popular in Cappadocia, often adding to its other-worldly appearance as the colorful aircraft rise above the Fairy Chimneys at sunrise. Let's embark on our own journey now and explore the horizons of Kyma 1.22.
See the overview of all changes in this release:
- Installation - Istio upgrade to 1.9.1, ORY charts update
- CLI - Option to deploy a specific Kyma branch
- Other - Inclusive language
With this release, we upgraded Istio from 1.8.2 to 1.9.1. You can find more details in the Istio 1.9.1 release notes.
In Kyma 1.22, ORY charts were updated to the latest versions from ORY repositories. These charts are not a direct copy because of many customizations and extensions specific to Kyma. The main changes resulting from this update are:
- The Hydra chart was updated to version 0.5.5, Hydra version 1.8.5. Find more details in the Hydra 1.8.5 release notes.
- The Oathkeeper chart was updated to version 0.5.7, Oathkeeper version v0.38.9-beta.1. Find more details in the Oathkeeper v0.38-9-beta.1 release notes.
- Hydra-Maester and Oathkeeper-Maester charts were updated accordingly.
The update also caused important changes in Hydra autoscaling (HPA) overrides. The ORY charts now provide a more recent and configurable set of overrides. Existing overrides defined in the
hpa.hydra entry were replaced by a configuration defined in
hydra.deployment.autoscaling. Take a look at the
values.yaml file for a default configuration.
Starting from this release, you can use the
kyma alpha deploy command to specify any branch of the official Kyma repository as a source to install or update Kyma. You can find more details in the CLI documentation.
Following good practices from GitHub, we adjusted our repositories to use more inclusive language and got rid of phrases such as "whitelist", "blacklist", and "slave" wherever possible. We also renamed the
master branches to
main in the following repositories:
To update the local setup of your forks, run these commands:
git branch -m master maingit fetch upstreamgit branch -u upstream/main main