Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deployment or StatefulSet #58

Open
jp83 opened this issue Jun 2, 2019 · 0 comments
Open

Deployment or StatefulSet #58

jp83 opened this issue Jun 2, 2019 · 0 comments

Comments

@jp83
Copy link

jp83 commented Jun 2, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant