You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I'm coming up to speed on k8s, and in particular testing with kube-plex, I'm wondering if perhaps the chart should deploy Plex media server as a StatefulSet instead of a Deployment. I can across this relevant discussion that made me wonder.
My main reasoning is the config directory that has all the metadata, watch history, and I think whatever they use to validate the claim token. Most importantly, every time I mess something up I keep having to helm --purge delete, and this wipes out the config dir, and then I have to relink the claim token. If I'm understanding correctly as a StatefulSet it would, by default, retain and reconnect to the existing PVC every time. The only thing I'm unsure of is if you can still have a NFS PVC for shared storage across other media acquisition deployments, which I guess could make you wonder if their own history should be retained as a StatefulSet as well.
@billimek I saw you in that thread as well and updated other relevant charts.
The text was updated successfully, but these errors were encountered:
As I'm coming up to speed on k8s, and in particular testing with kube-plex, I'm wondering if perhaps the chart should deploy Plex media server as a StatefulSet instead of a Deployment. I can across this relevant discussion that made me wonder.
helm/charts#1863
My main reasoning is the config directory that has all the metadata, watch history, and I think whatever they use to validate the claim token. Most importantly, every time I mess something up I keep having to helm --purge delete, and this wipes out the config dir, and then I have to relink the claim token. If I'm understanding correctly as a StatefulSet it would, by default, retain and reconnect to the existing PVC every time. The only thing I'm unsure of is if you can still have a NFS PVC for shared storage across other media acquisition deployments, which I guess could make you wonder if their own history should be retained as a StatefulSet as well.
@billimek I saw you in that thread as well and updated other relevant charts.
The text was updated successfully, but these errors were encountered: