Ververica Platform 2.14.1
Release Date: 2024-12-23
Changelog
Apache Flink®
Ververica Platform 2.14.1 supports the following versions:
- Apache Flink® 1.19
- Apache Flink® 1.18
- Apache Flink® 1.17
Ververica Platform 2.14.1 supports Apache Flink® 1.19, Apache Flink® 1.18, and Apache Flink® 1.17 under SLA.
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.17.2-stream6-scala_2.12-java8
- 1.17.2-stream6-scala_2.12-java11
- 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.0-stream3-scala_2.12-java8
- 1.19.0-stream3-scala_2.12-java11
- 1.19.0-stream3-scala_2.12-java17
For Spring Edition the following archives are available:
Improvements
Improved Kafka Connector Packaged with VVP Flink 1.17.2 to Support Multiple Topics
This release introduces an updated Kafka connector with improved partition assignment logic. The enhancement ensures a fair distribution of Kafka partitions across task slots, preventing data skew when consuming data from multiple topics.
This update is delivered with VVP Flink 1.17.2-stream6, which is the final Flink version bundling the Kafka connector.
Bug fixes
Fixed CRD validation Failure
In the VVP 2.14.0 we streamlined the Custom Resource Definitions (CRDs) to support openAPIV3Schema, providing an alternative to JSON schema validation. This enhancement offers schema validation directly within YAML-based CRD definitions.
However, the initial implementation introduced a bug that caused CRD validation failures, like the following Failed to reconcile k8s custom resource.
.
This bug has been resolved to allow the proper validation of the CR deployments and the reconciliation of them by the Kubernetes Operator.
Fixed YAML Editor to Prevent Namespace Defaults Invalid Text
This update resolves an issue in the Namespace Defaults YAML editor where users were provided with misleading feedback on updates to YAML definitions. Previously, the UI displayed a success message, even when the YAML contained invalid or erroneous text.
With this fix, the YAML editor now validates the configuration and provides explicit error messages on the UI, ensuring users are informed about invalid lines in their configurations.
Fixed Flink Deployment Editing to Prevent Invalid Values
This update addresses a validation gap in the Flink Deployment configuration fields. Previously, the UI allowed users to input invalid values (e.g., 0 for Max Job Creation Attempts) without providing any real-time feedback or warning. The underlying validator would silently reject the value on saving, leaving users unaware of the issue.
With this fix, the UI now enforces the allowed value range by providing reactive warnings and automatically replacing invalid inputs with the default value.
Fixed Audit Logs Bug on Autopilot Records
In version 2.14.1, we resolved a bug that caused intermittent errors when viewing Audit Logs in the VVP UI and API. The issue, specifically related to fetching records of Autopilot actions on deployment parallelism, is now fixed. This improvement ensures seamless user navigation and accurate log display across all views.
Vulnerability Fixes (outside of Apache Flink®)
- Upgraded tomcat to 10.1.34 to address CVE-2024-50379, CVE-2024-56337
- Upgraded netty to 4.1.115.Final to address CVE-2024-47535
Vulnerability Fixes (inside of Apache Flink®)
- Upgraded VVP Flink 1.17.2 to pymongo 4.10.1 to resolve CVE-2024-5629, CVE-2024-21506, GHSA-cr6f-gf5w-vhrc
- Upgraded VVP Flink 1.17.2 to numpy 1.24.4 to resolve CVE-2021-34141
Upgrade
As always, 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.10.1 --values custom-values.yaml