Christian Tardif
Christian Tardif
@justinrush OK so, apparently, something's not working well with my setup then. I have the POD IP of, right now, 10.42.2.60. My service IP is 10.43.90.23, and the exposedIP (the...
Got the same here as well (K8S 1.13.5). Added the 127.0.0.1 (as I thought it would be possible that the transcoder pod to try the loopback for connection back to...
Apparently, the latest plex image (**1.16.0.1226-7eb2c8f6f**) fixes the "_Connection refused_" issue. Updated the values file, then updated the helm deployment,. The logs of the transcoder now shows me that it...
How did you do it? In the helm chart only or if you need to do something else?
Ah! Got it, and I can now stream easily (well.... I can now see the video from Firefox in my workstation Another issue I have is the ability to "discover"...
You may likely be having to play with iproute2 and different routing tables. SHould do the job
@knucklehead101 And how did you manage to see your plex server outside of Kubernetes? As far as I know, DLNA is a multicast protocol which does not play well with...
Same issue after upgrading to v1.30.3+rke2r1 (latest at the moment)
In my case, I had to remove all secrets related to the metric servers: sh.helm.release.v1.rke2-metrics-server.vXX Once done, I just deleted the pod helm-install-rke2-metrics-server-xxxxx (from kube-system). The job recreated it and...
/remove-lifecycle stale