Zhoujing Wang, RM @Kyma, and Grzegorz Karaluch, Technical Writer @Kyma on March 15, 2023
Winter is almost over, and spring is just around the corner. If you look carefully, you’ll notice that here comes the sun, and with it, many interesting Kyma changes. Read on to find out more!
See the overview of all changes in this release:
- General - support for Kubernetes 1.25, migration guide actions, plans to remove the Blog and Community sections from the website
- Application Connectivity - use the
kyma-systemNamespace for Compass Runtime Agent
- Observability - New example on how to collect and export metrics based on OpenTelemetry
- Telemetry - Fixes and an update to third-party versions for logging and tracing
- Eventing - NATS server updated to
v2.9.14, Subscription updates
- Serverless - Node.js 18 runtime introduction, deprecation of Node.js 14 runtime, forthcoming removal of
Now, we officially support Kubernetes in version 1.25. For more information about changes in Kubernetes version 1.25, see the Kyma 2.9 release notes.
You'll need a few cleanup actions when updating to the newest version. For more information, read the 2.11-2.12 Migration Guide.
We're planning to restructure our Kyma website. Soon, the Community section will be removed, and the whole content will be kept in our Kyma
In addition, the Blog section will also be removed in the future. Worry not! All Kyma release notes will be available on the Kyma release page on GitHub and the blog posts on the SAP community portal.
Stay tuned for more information.
With Kyma 2.12, the Compass Runtime Agent component will use the
kyma-system Namespace instead of
When you upgrade Kyma from version 2.11 to 2.12, the old component deployed in the
compass-system Namespace won't be removed automatically.
If you're using Compass Runtime Agent, you must execute the script after successfully migrating from Kyma 2.11 to Kyma 2.12. If not, no additional action is required.
For more information, read the 2.11-2.12 Migration Guide.
- We have added a new example that illustrates collecting and exporting metrics using only OpenTelemetry technology.
- To decouple the Kyma components from the monitoring stack, all components have been refactored to use annotation-based metrics scraping instead of leveraging ServiceMonitors. Therefore, you must follow the 2.11-2.12 Migration Guide to clean up ServiceMonitors of the system components. Also, the bundled rules for Loki have already been removed. With that, the system components have no direct dependency on the Monitoring module anymore.
- As announced in the release notes of Kyma 2.11, the Monitoring module has been deprecated. All relevant documentation pages contain the deprecation note.
- A bug that caused Fluent Bit to print errors on startup has been fixed. Check this issue for more information.
- Fluent Bit has been updated to the 2.0.9 version.
- Since this release, the Kyma Dashboard extension for TracePipeline supports custom headers for OTLP outputs.
- Warnings at the startup of
otel-collectorhave been removed.
otel-collectorhas been updated to version 0.72.0.
The NATS server image has been updated to
v2.9.14. For more details, see the NATS server release notes.
With this release, we have upgraded event Subscriptions from
v1alpha2. This simplifies subscribing to events by removing the need for a prefix on the NATS/Jetstream backend. With the new version, we have also removed the previous modification of the event type during dispatching. The old Subscriptions will be upgraded automatically. For more details, check the updated tutorials.
With Kyma 2.12, we have introduced new Node.js 18 runtime for your Functions.
Because of the planned EOL for Node.js 14 we are planning to remove Node.js 14 from the list of the supported runtimes. For now, we recommend that you don’t use Node.js 14 as a runtime for your new Functions and re-configure all your existing Node.js 14 Functions to run on the latest available Node.js runtime. See this blog post to learn how to update existing Functions.
As of Kyma 2.6, the
serverless.kyma-project.io/v1alpha1 API has been deprecated.
We are getting close to the end of the 6-month depreciation period. Therefore, with the next Kyma release (2.13), we plan to stop supporting the deprecated API and support only
The conversion webhook that handles the conversion between the versions on the fly will be removed with Kyma 2.13.
Don't wait that long and adjust your Function manifests (YAML files) to the new version of the
serverless.kyma-project.io/v1alpha2 as soon as possible.