Expand the readMe

[NigelVanHattum]

I'm trying to set this up, bu I have no experience with GO and Helm. I'm not sure how to get started.

[simplyzee]

Hi @NigelVanHattum - is there anything, in particular, you're having trouble with?

[NigelVanHattum]

It's mostly how to get started, what is needed. Where do I need to execute it. How can I configure it. Do I need a running Plex server, do the nodes need to have acces to the media?

I may sound like a beginner, but I am :)

[Krm1t]

Although I'm currently stuck in getting kube-plex to work I do have some input to this.

• Prerequisites should include a working Kubernetes server and Helm be installed.
• Considering the above, it should probably be made clear that setting this up is not for beginners
  or at least you have to want to spend some time getting to know Docker and Kubernetes.
• While installing Kubernetes and Helm is out of scope for the readme it would be nice with a link to both. Could be included with the prerequisites.
• Although there are many ways of setting up pvc's there should probably be an optional suggestion on how to set it up between step 1 and 2.
• Currently plex claims are only valid for 5 minutes.
  This should be noted at step 1 perhaps in red text.
  I speak from experience as i created script to deploy kube-plex with the same token everytime and i didn't notice the timelimit over on the plex site.
• A section about debugging. This could just be links to different ways of debugging containers as explained over at Kubernetes.io

I think that was it

On a side note I would suggest creating a develop branch to minimize the risk of breaking the working copy of kube-plex.

[Wetteborn]

@Krm1t You wouldn't by any chance found any sort of break through?

I've gotten so far that I can access the pod running Plex server via browser (:32400/web). Howerver, I can't seem to get the Plex setup screen for the server itself. Just get the Plex login screen. If I login it takes me to the normal plex web interface (listing any other server tied to my account) and I don't have any way to setup the plex server running in the pod.

And the point about the Plex Claim Token, I fell prey to that too. Found out they have a 4min validation period. ha!

[Wetteborn]

And I totally just got it working...of course after I made a post.

I had to SSH tunnel to the pod.
sudo kubectl port-forward --namespace=plex 32400:32400

Had to add the --namespace=plex beacuse it's not the default namespace setup.

And then access it via localhost:32400/web apparently Plex will only go through setup using localhost not pod IP, cluster IP, or even 127.0.0.1.

[Krm1t]

@Wetteborn You actually got further than I do.
When I deploy my plex it enters a crash loop because the liveness and readyness probes gets a connection refused from the /identity url.
I have yet to find out why.

[Wetteborn]

@Krm1t Hmmm, yeah didn't run into that issue myself. I'm running Ubunutu 19.10 Server edition used Microk8s for my Kubernetes install, had to modifiy some of the commands to install kube-plex just to have it play friendly with Microk8s but mostly alias related things nothing over the top.

From my last comment I am having an issue with claiming the Plex instance but it's related to the facy my pod some reason can't resolve DNS requests. Not really a kube-plex issue, so I guess I'll have to do some digging to figure out what's causing that. Once I get that resolve, I'll see if the shim for transcoding is actually working. I can see the light at the end of the tunnel. ha!

[simplyzee]

@Krm1t Hmmm, yeah didn't run into that issue myself. I'm running Ubunutu 19.10 Server edition used Microk8s for my Kubernetes install, had to modifiy some of the commands to install kube-plex just to have it play friendly with Microk8s but mostly alias related things nothing over the top.

From my last comment I am having an issue with claiming the Plex instance but it's related to the facy my pod some reason can't resolve DNS requests. Not really a kube-plex issue, so I guess I'll have to do some digging to figure out what's causing that. Once I get that resolve, I'll see if the shim for transcoding is actually working. I can see the light at the end of the tunnel. ha!

I am also using Microk8s. I needed to enable the DNS addon to be able to use plex properly.

microk8s.enable dns

I’ve also set the service type for plex to NodePort. This way I can access the plex service via the NodePort that Kubernetes assigned. I also used this port for the remote access page so that I can see plex from the internet.

Cheers
Zee