Installation on OpenShift

Prerequisites

Version Compatibility

Please check Kubernetes Compatibility for the minimum required OpenShift version for your version of Ververica Platform.

Installation

In order to run Ververica Platform under the restricted Security Context Constraints (SCC), the securityContext.fsGroup entry of the Ververica Platform pod needs to be unset. For this, add the following entry to your ``values.yaml`` file to remove the default securityContext.fsGroup entry:

#
# EemptySecurity Context of Ververica Platform Pod. Comment out when running on Openshift.
#
securityContext: {}

We will use helm to template the Kubernetes resources, but depending on your OpenShift setup, we may or may not be able to use helm for the actual installation.

Installation with Tiller

If Tiller (the server-side component of helm) is available in your OpenShift cluster you can follow the instructions as outlined in Installation using Helm. This blog post in the OpenShift blog gives a good, hands-on introduction on how to get started with helm on OpenShift.

Installation without Tiller

If an installation with Tiller is not an option, you can first use helm template to generate the correct resource definitions and afterwards apply the generated resource definitions to the cluster:

Step 1: Templating the Resource Definitions

First, you use helm to template the Kubernetes resource definitions based on the provided configuration (values.yaml) and store results in the vvp-resources directory.

$ mkdir vvp-resources
$ helm template \
    --namespace my-project \
    --name vvp \
    --values values.yaml \
    --output-dir vvp-resources \
    ververica-platform-2.1.1.tgz

Step 2: Applying Resources to OpenShift Cluster

Afterwards, you use oc apply to create the resources in your OpenShift cluster.

$ oc apply --recursive --filename vvp-resources