Herzlich Wilkommen! We left the windy Amsterdam, but we're staying within the area of the West Germanic group of languages, this time stopping at Berlin, the capital of Germany and a world city of culture, politics, media, and science. But don't be fooled by the great historical buildings, universities, and museums. Berlin does a great job at combining this rich heritage with the new and avant-garde, and it does all that ahead of the rest, too. Contemporary art, numerous festivals, artisanal coffee shops, craft beer, and the famous nightlife are just part of it. Just like Berlin, Kyma also combines a solid foundation with innovation, providing high quality that will not cost you an arm and a leg. This time, we focused on CLI, Monitoring, Eventing, and Serverless, so grab a cup of (artisanal) coffee, and read on.
CAUTION: In this release, the Eventing component was switched completely from Knative to NATS. Before upgrading to 1.21, read the Migration Guide for details on Troubleshooting and Upgrade.
See the overview of all changes in this release:
- CLI - Alpha commands stabilized,
runcommand available locally
- Monitoring - Dynamic data source configuration, deriving traces from Loki logs
- Eventing - Knative-based eventing replaced by NATS
- Serverless - Node.js 10 deprecation
- Known issues - Tracing not working with the new eventing
We've recently added new alpha commands:
alpha provision k3s,
alpha delete, and
In this release, we stabilized these commands, and they are now ready for beta testing.
For more information, read the alpha command usage examples and the command help.
Kyma CLI provides a set of helpful commands for Function developers.
They support developers in starting development, pushing local code to the Runtime, and syncing Functions.
In this release, we have added one more command to facilitate your developer experience even more.
run command allows you to run the Function's code locally, before applying it to the Kyma runtime.
For more information, read the Kyma CLI documentation.
We enabled the Grafana feature to collect and load data source definitions from Kubernetes ConfigMaps at startup. By doing that, we were able to move the individual pre-configured data sources into the related components. For example, the data source for Loki moved into the Logging component. This way, we improved the resource organization.
The Loki data source for Grafana now contains a new derived field for
By default, Grafana checks every log in the Grafana View for the
If it finds this
traceId, it displays the link to the corresponding Jaeger trace.
For more information about derived fields, read the Grafana documentation.
In this release, we removed Knative-based eventing. The new Eventing component is based on NATS with a Kyma-specific Subscription custom resource (CR). For upgrade scenarios, refer to the Migration Guide.
For more information on the new eventing, read the documentation.
Node.js 10 release reaches end-of-life on Apr 30, 2021, and its base image will be deprecated. Following the recommendations from Node.js, we are planning to remove Node.js 10 from the list of supported runtimes in the next release. That's why we recommend that you configure all your Node.js 10 Functions to run on the Node.js 12 runtime. See the list of notable changes since Node.js 10 LTS.
For more information on Node.js 10 deprecation, read about Node.js releases.