Skip to main content
Version: 2.14

Ververica Platform 2.5.1

Release Date: 2021-08-18

Changelog

This release adds support for Apache Flink® 1.12.5 and Apache Flink® 1.13.2.

Please check out the Apache Flink® 1.12.5 release announcement for details about this Apache Flink® release.

Please check Ververica Platform Docker Images for all available Apache Flink® images and additional tags.

Improvements
  • Updated AWS dependencies to support IAM Roles for Service Accounts (IRSA) on EKS clusters.

Please check out the Apache Flink® 1.13.2 release announcement for details about this Apache Flink® release.

Please check Ververica Platform Docker Images for all available Apache Flink® images and additional tags.

Improvements
  • Updated AWS dependencies to support IAM Roles for Service Accounts (IRSA) on EKS clusters.

Improvements

Rest API

  • Improved error message when trying to create a deployment without a deployment target.
  • Improved error message when sending requests containing invalid namespace names.

UI

  • Forking a Deployment from a Savepoint no longer changes spec.restoreStrategy to LATEST_SAVEPOINT if it was LATEST_STATE before.
  • Links to the Apache Flink® UI are available earlier during the Deployment lifecycle. In particular, it should no longer happen that they remain inactive throughout the lifecycle of a batch job.

###Bug Fixes

Deployments

  • Using placeholders in the Apache Flink® configuration option high-availability.storageDir works now.
  • Fixed an issue with updating deployment defaults in certain situations - e.g. when switching from using deploymentTargetId to using deploymentTargetName.

Savepoints

  • When adding a Savepoint manually, metadata.origin will automatically be set to COPIED and must no longer be specified.
  • Savepoints with invalid metadata.jobId can be deleted now.
  • Deleting a Savepoint without spec.savepointLocation no longer causes all other Savepoints with no location to be scheduled for deletion as well. Instead, only the original Savepoint will be affected.

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 5.1.1 --values custom-values.yaml