Cloud Native Compiler Release Notes

To avoid restarts of the Gateway pod when a large number of clients try to write profile logs at the same time, a default limit has been configured.

Upgrade from version 1.6.0 can be done with a helm upgrade, as described on Upgrading Cloud Native Compiler.

Gateway pod gets restarted when large number of clients try to write profile simultaneously.

JVMs released before CNC 1.6.1 use HTTP for uploads of the compiler engine. Since version 1.6.1, gRPC is used and the HTTP port is disabled by default in values.yaml. Because of this, these JVMs will not be able to upload their appropriate compiler engine to CNC.

When a CNC version prior to 1.6.1 already has been used and upgraded, the older JVMs will keep working with CNC, because the upload is not needed anymore.

The first attempt to download a previously existing profile, after CNC upgrade to 1.6.1 can fail with a timeout.