Ververica Platform 2.2.2
Release Date: 2020-10-27
Changelog
Bug Fixes
- The requested CPU resources of a Deployment must be greater or equal to 0.1. Prior to this release, it was possible to configure lower values and the init container CPU request was hard coded to 0.7. The configured CPU request is now assigned to all containers of the respective Flink pod.
- The Artifact type has been inlined in the Swagger spec of Application Manager. This will allow HTTP clients generated from the Swagger spec to set the Artifact section of Deployments.
Apache Flink® 1.11.2
-
For Stream Edition the following Apache Flink® Docker images are available. Please check Ververica Platform Docker Images for all available Apache Flink® images and additional tags.
1.11.2-stream2-scala_2.111.11.2-stream2-scala_2.12
-
For Spring Edition the following / archives are available
Vulnerability Fixes
The following security vulnerabilities have been fixed compared to 1.11.2-[stream|spring]1:
None
Apache Flink® 1.10.2
-
For Stream Edition the following Apache Flink® Docker images are available. Please check Ververica Platform Docker Images for all available Apache Flink® images and additional tags.
1.10.2-stream2-scala_2.111.10.2-stream2-scala_2.12
-
For Spring Edition the following / archives are available
Vulnerability Fixes
The following security vulnerability in non-Flink components of Ververica Platform have been fixed compared to 2.2.1:
CVE-2020-5421, CVE-2020-7598, CVE-2020-8203, CVE-2020-14344, CVE-2020-14363, CVE-2017-18869, CVE-2019-20149
Charts
- The Ververica Platform Helm charts now support to attach additional custom volumes to the Ververica Platform containers. Please checkout the Helm charts default values for details.
Upgrade
We recommend upgrading via Helm using the following commands:
helm repo add ververica https://charts.ververica.com
helm upgrade [RELEASE] ververica/ververica-platform --version 4.2.2 --values custom-values.yaml