Closed wrender closed 4 years ago
I was able to resolve this by deleting the ingress, deleting the service, and then setting the following to allow host networking in the deployment. I also had to delete the ports: defined in the deployment. This would only be useful if you just want to run one Plex instance, on a single server type of thing.
spec:
template:
spec:
hostNetwork: true
Now if a remote plex user connects in from the internet -> router. It is recognized as a remote user, and a local lan TV connection is a local user in Plex.
I was able to resolve this by deleting the ingress, deleting the service, and then setting the following to allow host networking in the deployment. I also had to delete the ports: defined in the deployment. This would only be useful if you just want to run one Plex instance, on a single server type of thing.
spec: template: spec: hostNetwork: true
Now if a remote plex user connects in from the internet -> router. It is recognized as a remote user, and a local lan TV connection is a local user in Plex.
Hi wrender,
Can you please clarify how you added this? I can't get remote access enabled on kubernetes deployment, I have deployed plex using helm charts.
Fantastic helm chart thanks! I think this is just my confusion with networking in Kubernetes, but I am having issues with Plex distinguishing between local and remote traffic with my Plex installation using this helm chart. Plex seems to always see traffic as coming from my virbr0 ip of 192.168.1.122/24 whether it is coming from a port forward on the router, or going to Plex from TVs on the local lan.
I have the following settings:
kubePlex: enabled: false
service: type: NodePort port: 32400 nodePort: 32400
ingress: enabled: true hosts:
claimToken: claim-myclaimtoken
persistence: data: storageClass: local-path claimName: plex-data config: claimName: plex-config
Copy these manually to the container settings in Kubernetes
NVIDIA_VISIBLE_DEVICES=all
NVIDIA_DRIVER_CAPABILITIES=compute,video,utility
CUDA_DRIVER_CAPABILITIES=compute,video,utility
ADVERTISE_IP=http://192.168.2.6:32400