Skip to main content

Ververica Platform 3.0.1

Release Date: 2026-02-13

Ververica Platform 3.0.1 is a patch release that enhances platform stability, expands deployment flexibility, and resolves key issues identified in the initial 3.0.0 release. This update introduces support for advanced pod-level customizations, improves security through Kubernetes Secret integration for credentials and licenses, and supports post-installation blob storage configuration.

Ververica Platform 3.0.1 supports VERA 4.1 and Apache Flink® 1.20.

New Features and Improvements​

Allow Pod-Level Customization via YAML​

Ververica Platform now supports pod-level customization via YAML configuration. You can define labels, annotations, tolerations, security contexts, imagePullSecrets, and more for JobManager and TaskManager pods. Full Kubernetes pod templates are also supported, allowing advanced customizations such as sidecars, init containers, and volumes. This enhancement improves flexibility and integration with enterprise Kubernetes environments.

Provide Blob Storage Credentials via Kubernetes Secrets​

You can now manage blob storage credentials as Kubernetes Secrets. This allows secure distribution of access credentials for S3, Azure Blob, HDFS, and other storage providers to Flink jobs running in Kubernetes. Credentials can be referenced or mounted using native Kubernetes secret mechanisms, improving security, flexibility, and compliance while simplifying configuration.

Support Post-installation Blob Storage Update​

Ververica Platform 3.0.1 is now able to receive configuration updates about the utilized Blob Storage. This update addresses the need to configure Blob Storage after the installation of the platform without uninstalling the platform first to have the configuration take effect. The scope of the improvement focuses on new Flink deployments and not on the already running jobs.

Provide License via Kubernetes Secret in Helm Charts​

You can now supply the Ververica license via a Kubernetes Secret mounted into the platform pods, instead of embedding the license content directly in values.yaml. This improves security and operational hygiene by enabling GitOps-friendly license management and reducing the risk of leaking license data through Helm configuration files or pipelines.

Bug Fixes​

Fixed Intermittent Kubernetes API Authentication Loss in vvp-agent​

Resolved an issue where the vvp-agent pod could intermittently lose authentication to the Kubernetes API. When this occurred, UI operations such as starting or stopping session clusters and Flink deployments would fail. This fix ensures stable and continuous authentication, restoring reliable operational control.

Upgrade​

To upgrade Ververica Platform to version 3.0.1, run the following Helm command:

helm upgrade --install <RELEASE_NAME> \
  oci://registry.ververica.cloud/platform-charts/ververica-platform \
  --version 3.0.1 \
  --namespace vvp-system \
  --values values.yaml

Migration from 2.x​

If you are migrating from Ververica Platform 2.x to the 3.0.x series, please note:

  • Baseline Requirement: You must be on VVP 2.15.x running Flink 1.20 before initiating an upgrade to 3.0.x.
  • Licensing: Ververica Platform 2.x licenses are not valid for 3.0.x. You must obtain a new license.
  • Full Details: For a complete list of architectural changes and migration steps, see the Ververica Platform 3.0.0 Release Notes.
On this page