Skip to content
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.

Plex Media Server chart #3289

Closed
munnerz opened this issue Jan 10, 2018 · 8 comments
Closed

Plex Media Server chart #3289

munnerz opened this issue Jan 10, 2018 · 8 comments

Comments

@munnerz
Copy link
Collaborator

munnerz commented Jan 10, 2018

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 munnerz/kube-plex#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! 😄

@mattfarina
Copy link
Contributor

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.

@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 11, 2018
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 11, 2018
@fejta-bot
Copy link

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

@davidkarlsen
Copy link
Member

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jun 11, 2018
@davidkarlsen
Copy link
Member

/reopen

@k8s-ci-robot
Copy link
Contributor

@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.

@davidkarlsen
Copy link
Member

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

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

No branches or pull requests

5 participants