search

adambkaplan / plex-operator

Yet another Plex operator for Kubernetes
Apache License 2.0
17 stars 4 forks source link

support existing volume claims #10

Open brunnels opened 3 years ago

brunnels commented 3 years ago

I have several nfs exports from my NAS that I already have volume claims configured for. Can you add support configure the volumes and volumeMounts for the data persistence?

volumes:
  - name: pvc-movies
    persistentVolumeClaim:
      claimName: pvc-movies
  - name: pvc-tv
    persistentVolumeClaim:
      claimName: pvc-tv
  - name: pvc-music
    persistentVolumeClaim:
      claimName: pvc-music
  - name: pvc-pictures
    persistentVolumeClaim:
      claimName: pvc-pictures

volumeMounts:
  - name: pvc-movies
    mountPath: "/data/movies"
  - name: pvc-tv
    mountPath: "/data/tv"
  - name: pvc-music
    mountPath: "/data/music"
  - name: pvc-pictures
    mountPath: "/data/pictures"
adambkaplan commented 3 years ago

There's actually two times in this request to address:

  1. Allow operators to bring their own PVC. The current operator generates a PVC using a volume claim template, which users may not want.
  2. Support multiple volumes for the data source. This is doable, but may get tricky. I don't think supporting multiple volumes for the config and transcode volumes make sense.

Do many folks use separate NFS exports/storage volumes for their media collections?

trevor-viljoen commented 3 years ago

Do many folks use separate NFS exports/storage volumes for their media collections?

My media is separated by content category. For instance: Music, Movies, TV_Shows, etc. They are all on separate exports currently. I'm looking to migrate my existing Plex VM to my OKD cluster to free up some more resources.