Ververica Platform 2.3.0

Release Date: 2020-10-21


Helm Charts

Additional memory is allocated to the gateway container hosting the SQL service. If memory is scarce in your environment and you don’t use the SQL functionality yet, feel free to limit the requested memory as follows:

      memory: 1Gi
      memory: 1Gi

If on the other hand, you expect many concurrent SQL users, we recommend to increase the available memory as described in the advanced SQL configuration guide.

Other Changes

Session Clusters

You can now use Ververica Platform to manage Apache Flink® Session Clusters. In this release, the primary use case of Session Clusters in Ververica Platform is running preview queries submitted via the SQL editor. Full support for Session Clusters is planned for Ververica Platform 2.4.0 including:

  • Deployments on Session Clusters
  • SSL
  • Kubernetes-based Flink Jobmanager failover
  • Reactive cluster scaling

So far, we have distributed our fork of Apache Flink® via Docker images (Stream Edition) and archives (Spring Edition). These Docker images only contain the binary distribution of Apache Flink® and, hence, do not cover all of the components that we support commercially: connectors, for example, are not part of the binary distribution.

In order to support you more efficiently, we will, from now, publish all dependencies for each release of our distribution of Apache Flink in a public Maven repository hosted under Please check Packaging your Application for how to integrate our repository into your build system.

Web User Interface


The navigation side-bar has been reworked, specifically:

  • Secret Values was moved to Administration
  • Namespaces was moved to the namespace picker and is now called Manage Namespaces.
  • A top-level SQL section was added.
  • A Session Cluster page was added under Deployments.

Deployment Form Improvements

You can now create your first Deployment Target per namespace right in the Deployment creation form instead of the Deployment Targets page. Similarly, you can upload JAR artifacts directly from the Deployment creation form, not only via the Artifacts page.

Additional Dependencies for JAR Artifacts

For JAR Deployments, you may provide additional dependencies besides your main artifact containing your Apache Flink® program.

  kind: jar
  jarUri: https://artifacts/flink-job.jar
    - https://artifacts/flink-connector.jar
    - https://artifacts/additional-library.jar


We recommend upgrading via Helm using the following commands:

$ helm repo add ververica
$ helm upgrade [RELEASE] ververica/ververica-platform --version 4.3.0 --values custom-values.yaml


As mentioned in the Helm Charts section, the default resource requirements of Ververica Platform has changed with this release.