[jira] [Commented] (FLINK-24332) Support to mount a dynamically-created persistent volume claim per TaskManager

["Yang Wang (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-24332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17806763#comment-17806763 ] 

Yang Wang commented on FLINK-24332:
-----------------------------------

We do not need this feature now since Kubernetes has already supported ephemeral volume[1].

 

[1]. [https://kubernetes.io/docs/concepts/storage/ephemeral-volumes/]

 

 
{code:java}
apiVersion: v1
kind: Pod
metadata:
  name: taskmanager-pod-template
spec:
  containers:
    # Do not change the main container name
    - name: flink-main-container
      volumeMounts:
        - mountPath: /opt/flink/volumes/ephemeral
          name: ephemeral-volume
        - mountPath: /opt/flink/log
          name: flink-logs
  volumes:
    - name: flink-logs
      emptyDir: { } 
    - name: ephemeral-volume
      ephemeral:
        volumeClaimTemplate:
          spec:
            accessModes: [ "ReadWriteOnce" ]
            storageClassName: "<replace-with-valid-storage-class-name>"
            resources:
              requests:
                storage: 1Gi{code}
 

 

> Support to mount a dynamically-created persistent volume claim per TaskManager
> ------------------------------------------------------------------------------
>
>                 Key: FLINK-24332
>                 URL: https://issues.apache.org/jira/browse/FLINK-24332
>             Project: Flink
>          Issue Type: New Feature
>          Components: Deployment / Kubernetes
>            Reporter: Yang Wang
>            Priority: Major
>
> Pod template could be used to mount a same PVC for all the TaskManagers. However, in many cases, users need to mount dynamically-created persistent volume claim for each TaskManager.
>  
> Refer to [https://lists.apache.org/thread.html/r08ed40ee541c69a74c6d48cc315671198a1910dbd34fd731fe77da37%40%3Cuser.flink.apache.org%3E] for more information.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)