Resource usage instructions of K8s PVC

The support for pvc resource(mount file resources such as checkpoint/savepoint/logs and so on) is based on pod-template at current version。

Users do not have to concern the Native-Kubernetes Session.It will be processed when Session Cluster is constructed .Native-Kubernetes Application can be constructed by configuring on StreamPark webpage using pod-templatejm-pod-templatetm-pod-template.


Here is a brief example. Two PVC flink-checkpointflink-savepoint should be constructed in advance

Kubernetes PVC

‘pod-template’ can be configured as below :

  1. apiVersion: v1
  2. kind: Pod
  3. metadata:
  4. name: pod-template
  5. spec:
  6. containers:
  7. - name: flink-main-container
  8. volumeMounts:
  9. - name: checkpoint-pvc
  10. mountPath: /opt/flink/checkpoints
  11. - name: savepoint-pvc
  12. mountPath: /opt/flink/savepoints
  13. volumes:
  14. - name: checkpoint-pvc
  15. persistentVolumeClaim:
  16. claimName: flink-checkpoint
  17. - name: savepoint-pvc
  18. persistentVolumeClaim:
  19. claimName: flink-savepoint

There are three ways to provide the dependency when using rocksdb-backend.

  1. Flink Base Docker Image contains the dependency(user fix the dependency conflict by themself);

  2. Put the dependency flink-statebackend-rocksdb_xx.jar to the path Workspace/jars in StreamPark ;

  3. Add the rockdb-backend dependency to StreamPark Dependency(StreamPark will fix the conflict automatically) :

    rocksdb dependency


We will provide a graceful way to generate pod-template configuration to simplify the procedure of k8s-pvc mounting in future version.