Warning: This document is for an old version of Ververica Platform. The latest version is v2.1.

Installation & Upgrades

Prerequisites

Kubernetes

Ververica Platform is designed to be deployed on Kubernetes: all platform components as well as the Apache Flink Deployments it manages run as Docker containers on Kubernetes.

Durable Storage

Apache Flink relies on periodic state snapshots to durable storage for fault-tolerance and upgrades. In order to make use of these features, the platform is configured with a Storage Providers during installation. Supported storage backends include NFS as well as the blob storage services of all popular public cloud providers. Please see Storage Providers for details.

Preparation

Kubernetes ServiceAccount

Ververica Platform requires access to the Kubernetes API so it can create and manage resources to run Flink applications.

Therefore Ververica Platform must be deployed in Kubernetes with a ServiceAccount that grants it the necessary permissions to manage resources in the same Kubernetes namespace it is deployed in.

The necessary RBAC role is created automatically by the included Helm chart, but for other platforms like OpenShift some manual steps may be required to ensure Application Manager has all the required permissions.

Ververica Platform Docker Images

Before proceeding you need to decide how to access the Ververica Platform Docker images: either you use Ververica’s public Docker registry or you host the Docker images internally. Please see Ververica Platform Docker Images for details on both options.

Installation

You are now ready to proceed with the installation. For installing Ververica Platform with helm please see Installation using Helm.

Note

Ververica Platform include and depend on open source software. The distribution of Ververica platform contains a licenses/ directory which documents the software packages used and includes copies of their licenses.