Charts: Plex Media Server chart

Created on 10 Jan 2018 · 8Comments · Source: helm/charts

I've developed a Plex Media Server helm chart. I'm considering submitting it upstream if it would be accepted? https://github.com/munnerz/kube-plex

Currently it also enables 'remote transcoding' (dispatching transcode jobs as individual pods across the Kubernetes cluster). I've opened https://github.com/munnerz/kube-plex/issues/14 to provide the option to disable this behaviour, which I imagine will make the more paletable upstream. I'd love to get some feedback on what the upstream requirements would be for this! 😄

Source

munnerz

👍3

Most helpful comment

@munnerz can this be re-attempted? I'd love to see it in the official repo!

davidkarlsen on 9 Jul 2018

👍12

All 8 comments

As a plex user, I'm happy to see this. And, I like the idea of using jobs to transcode media. That's a good direction to go in. I think you're idea of using the shim and transcoding as an opt-in (or opt-out).

In the chart itself, this mostly looks well put together. I do have a couple notes:

Use tagged versions of images (for reproducibility) instead of latest.
Use apps/v1beta2 instead of app/v1. Only Kubernetes 1.9 supports apps/v1 and we support more than that.

Please feel free to ping me if you create a PR for the chart here.

mattfarina on 11 Jan 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 11 Apr 2018

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

fejta-bot on 11 May 2018

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot on 10 Jun 2018

/remove-lifecycle rotten

davidkarlsen on 11 Jun 2018

/reopen

davidkarlsen on 11 Jun 2018

@davidkarlsen: you can't re-open an issue/PR unless you authored it or you are assigned to it.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.