Wojciech Sołtys, RM @Kyma, and Grzegorz Karaluch, Technical Writer @Kyma on November 22, 2022
Roses are red, violets are blue, and Kyma is ready with the new updates for you. This release comes with some interesting changes. For example, now we officially support Kubernetes in version 1.24. Read on to find out more about the 2.9 release!
See the overview of all changes in this release:
- General - support for Kubernetes 1.24
- Observability - Loki deprecation, component updates
- Telemetry - a preview of how a trace backend can be integrated in the future
- Serverless - Node.js 12 runtime deprecation
- CLI - Function commands adjusted to the new API version
- Eventing - NATS server updated to
With this Kyma release, Kubernetes gets officially supported in version 1.24. The default settings for the provision commands provided by Kyma CLI were also adjusted. For more details on this version, read the Kubernetes release notes.
While working on that, we've already taken major steps towards the next Kubernetes version 1.25 by cleaning all PodSecurityPolicies (PSP) and revising all SecurityContexts. Remember that you may need to replace your custom PSPs with the new security standards; click here for more information.
As we removed the generic Kyma PSP, your Pods may be prevented from being deployed now as the providers’ default policies are not fitting. During the upgrade to this Kyma version, you might need to introduce proper PSPs to compensate for the removal unless you've already disabled the PSP admission controller and switched to the new security admission model.
Follow this migration guide to learn how to clean up your Kyma resources from the PSP leftovers when you upgrade from Kyma 2.8 to 2.9.
As you've probably learned from this blog post, we decided to deprecate the Loki installation which is part of the Logging component. Please start the transition to alternative solutions. The actual removal will not happen sooner than in six months, with Kyma 2.15 at the earliest.
As announced in the release notes for Kyma 2.6, the Fluent Bit component got migrated from the Logging component to the Telemetry component. With this Kyma version, the old Fluent Bit setup finally got removed from the Logging component. Before you can upgrade to Kyma 2.9, you must follow this migration guide if you have not switched to the telemetry component yet.
In this release, we also updated Prometheus to version 2.39.1, Prometheus Operator to version 0.60.1, and OAuth2 Proxy to version 7.4.0.
For more details, see the release notes for Prometheus, Prometheus Operator, and OAuth2 Proxy.
We are actively working on the possibility of integrating your trace backend based on OTLP. You can try out the first preview version by following this new trace demo. Give it a try and feel free to provide feedback on the related GitHub issue.
Node.js 12 has reached the end of its life. Therefore, followed by the depreciation of Node.js 12 Serverless runtime, we decided to finally remove it from the list of the available Function runtimes.
Your Node.js 12 Functions' workloads will continue to run, but you will not be able to edit them without changing the
runtime field. Sooner or later, you must change the spec of your existing Node.js 12-based Functions and change the
runtime field to either
For more information about the Node.js 12 deprecation, see the Kyma 2.1 release notes.
Following the recent API changes in Serverless, the related Kyma CLI commands were adjusted to comply with the
serverless.kyma.project.io/v1alpha2 API version.
NATS server was updated to version 2.9.6. For more information read the NATS server v2.9.6 release notes.
The stream setup was modified for the case of full message storages. This state will now lead to the rejection of new messages and the return of error code
507. These changes were introduced to prevent the deletion of old messages.