Accessing Ververica Platform

There are multiple ways to access Ververica Platform, depending on your environment.

Port Forwarding

Kubernetes' built-in Port Fowarding capabilities can be used for quick setup, testing purposes, and for production environments where Ingress is not available or not allowed.

In the example below, assuming you have deployed Ververica Platform using Helm with release name ververica-platform into Kubernetes namespace vvp-system, you can use this command to forward the Ververica Platform REST API and Web User Interface locally on port 8080:

1kubectl -n vvp-system port-forward service/api-gateway 8080:8080

You can open the Web user interface using the address http://localhost:8080.

Kubernetes Ingress

For production environments where Kubernetes Ingress is available, Ververica Platform can be accessed without using Port Forwarding (#port-forwarding). This is recommended for environments where users of Ververica Platform do not need to have access to the underlaying Kubernetes cluster infrastructure.

** From here this has to be checked. We need to verify the correct Service name that is created ** The Helm chart creates a Service called <release-name>-ververica-platform, which can be accessed directly or referenced from an Ingress.

Examples

1. A LoadBalancer Service that exposes Ververica Platform using the release name and Kubernetes namespace above:

1apiVersion: v1
2kind: Service
3metadata:
4  name: my-service
5  namespace: my-namespace
6spec:
7  type: LoadBalancer
8  ports:
9  - name: appmanager
10    port: 80
11    targetPort: 8080
12  selector:
13    app: vvp-ververica-platform
14    component: appmanager

1. An Nginx Ingress configured to serve Ververica Platform from an internal domain:

1apiVersion: extensions/v1beta1
2kind: Ingress
3metadata:
4  annotations:
5    kubernetes.io/ingress.class: nginx
6  name: my-ingress
7  namespace: my-namespace
8spec:
9  rules:
10  - host: ververica-platform.internal
11    http:
12      paths:
13      - backend:
14          serviceName: vvp-ververica-platform
15          servicePort: 80
16        path: /

If you set a context path i.e. a subpath instead of /, then remember to modify the path appropriately in the Ingress configuration. It must match the context path.

Accessing VVP UI from a Subpath

You might want to make the Ververica Platform UI accessible from a subpath rather than the root path. To do so, set the context path using Spring Boot configurations.

1. Using topLevelConfig in your YAML configuration:

1topLevelConfig:
2  server:
3    servlet:
4      contextPath: /vvp

1. Using an environment variable:

1env:
2  - name: SERVER_SERVLET_CONTEXT_PATH
3    value: /vvp

After setting the context path, when you deploy Ververica Platform the UI is accessed from the specified subpath.

The subpath has the format http://localhost:port-number/<context-path>/app. For example:

1http://localhost:8080/vvp/app