Accessing Ververica Platform

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

During testing and initial setup, the easiest approach is to use the port forwarding support built into Kubernetes. For example, if you have deployed Ververica Platform using Helm with release name vvp into Kubernetes namespace my-namespace, you can use this command to forward the Ververica Platform REST API and Web User Interface locally on port 8080::

kubectl -n my-namespace port-forward service/vvp-ververica-platform 8080:80

In a production environment, it is recommended to use a Kubernetes Ingress or Service to access Ververica Platform. The Helm chart creates a Service called <release-name>-ververica-platform, which can be accessed directly or referenced from an Ingress.

Examples

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

    apiVersion: v1
    kind: Service
    metadata:
      name: my-service
      namespace: my-namespace
    spec:
      type: LoadBalancer
      ports:
      - name: appmanager
        port: 80
        targetPort: 8080
      selector:
        app: vvp-ververica-platform
        component: appmanager

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

    apiVersion: extensions/v1beta1
    kind: Ingress
    metadata:
      annotations:
        kubernetes.io/ingress.class: nginx
      name: my-ingress
      namespace: my-namespace
    spec:
      rules:
      - host: ververica-platform.internal
        http:
          paths:
          - backend:
              serviceName: vvp-ververica-platform
              servicePort: 80
            path: /