Skip to main content
Version: 2.15

Ververica Platform 2.15.5

Release Date: 2026-01-23

Changelog​

Ververica Platform 2.15.5 supports the following versions:

  • Apache Flink® 1.20
  • Apache Flink® 1.19
  • Apache Flink® 1.18

Ververica Platform 2.15.5 supports Apache Flink® 1.20, Apache Flink® 1.19, and Apache Flink® 1.18 under SLA.

For Stream Edition:

  • 1.18.1-stream5-scala_2.12-java8
  • 1.18.1-stream5-scala_2.12-java11
  • 1.18.1-stream5-scala_2.12-java17
  • 1.19.3-stream2-scala_2.12-java8
  • 1.19.3-stream2-scala_2.12-java11
  • 1.19.3-stream2-scala_2.12-java17
  • 1.20.3-stream1-scala_2.12-java8
  • 1.20.3-stream1-scala_2.12-java11
  • 1.20.3-stream1-scala_2.12-java17

For Spring Edition the following archives are available:

Improvements​

Improved logging to capture Kubernetes timeouts configuration​

We have identified the need to capture Kubernetes ApiClient configuration to support the debugging of more sophisticated Kubernetes clusters operations on the user infrastructure. Clarifying within the Ververica Platform logs the Kubernetes ApiClient configuration allows the SREs responsible for the infrastructure to better identify possible misalignments at the configuration of the various dependant systems for the seamless operation of the Ververica Platform. The logs will automatically appear in the platform pods.

Bug Fixes​

An issue was identified in Ververica Platform 2.15.4 where the Flink UI and the Swagger UI would not render as expected due to the strict CSP header that has been applied. This regression introduced the need to configure the CSP header on the server side of the user to override the erroneous configuration of the platform. With this fix, the CSP header is relaxed and it has been turned into a configurable value. Use the following in the values.yaml to enable it:

vvp:
  gateway:
    contentSecurityPolicy: "default-src 'self'; script-src 'self' 'unsafe-inline'; object-src 'none'; style-src 'self' 'unsafe-inline';"

Fixed Cursor Issue When Editing Deployment Names​

Fixed an issue where the cursor would jump to the end of the deployment name when deleting characters. You can now edit deployment names smoothly, with the cursor staying in the correct position.

Upgrade​

We recommend upgrading via Helm using the following commands:

$ helm repo add ververica https://charts.ververica.com
$ helm repo update
$ helm upgrade [RELEASE] ververica/ververica-platform --version 5.11.5 --values custom-values.yaml
On this page