![plex media server connection refused plex media server connection refused](https://www.rapidseedbox.com/wp-content/uploads/2016-07-28_1418-1.png)
I can run monitoring solutions that understand Kubernetes and can listen to all sorts of signals Kubernetes and the apps within make. I can run a log collection system that automatically collects all logs from all containers, and makes it easily searchable. I can run cert-manager, with automatically makes LetsEncrypt certificates, and makes them available for the ingress controller. I also run an Ingress Controller, which can handle stuff like terminating TLS, and various other stuff with network traffic coming into the cluster. This also allows me to run many different services on a single port, but different IPs. I have MetalLB, which allows me to easily assign a real network IP to anything running in my cluster. It can even show me a diff of what's in the repo and what's actually running in the cluster. I have ArgoCD, which watches the above mentioned git repository, and allows me to roll out any changes with the click of a button, or even automatically. Kubernetes allows people to build general tools that can do really powerful stuff. I have all my Kubernetes specifications stored in a git repository. Kubernetes allows you to clearly and declaratively describe everything in it. Kubernetes provides a uniform way of running any container. The container can only modify the data you have mounted into it, and can only expose the ports you specify. This means that you can relatively easily reason about what a container can do. Most containers clearly specify relevant volumes (data locations) and exposed ports. You don't have any lingering cruft lying around in. If you ever decide to remove something again, it's a simple matter of deleting the container and the image, and that's it. You will never have problems with some dependency library being discontinued and annoying to obtain.ĭue to bundling all the dependencies, you will also never have problems with one app requiring version 3 of some library and another requiring version 2. That means that as long as you can obtain the container, you can run it. I'll list both container benefits and Kubernetes benefits below:Ī container bundles all it's dependencies. I just happen to like the way Kubernetes handles things.īoth containerization and Kubernetes come with a number of benefits and drawbacks. I could have achieved everything I did without using Kubernetes. Kubernetes is a really powerful tool, but it is likely unsuitable for most Plex and home users. I also work professionally with Kubernetes.
![plex media server connection refused plex media server connection refused](https://kibu.beegeescover.pl/templates/64af9ff6ec07d70d68e9adf4e68843a5/img/f909e97feb124fca0cfaec5971e44150.jpg)
I set up a home server running Kubernetes with Plex within the last 2 weeks. Its probably well known that its not a good idea to have the config folder on NFS, but this post is for people searching for it hanging on Kubernetes. Changing to a iSCSI volume fixed the issue. The config folder was mounted NFS and not a local share like docker. This led me to conclude its not in fact networking, but something else. Then I noticed that un-authenticated connections (which return a 4xx forbidden http response) worked perfectly, even during the hangs. I thought it was networking, and spent a lot of time trying host-networking, and even capturing packets using wireshark and TCP streams using fiddler, none of which gave me much of a clue. Ive used it in regular docker for years, and its been perfect, but moving to Kubernetes caused it to become flaky.įor the google searchers, the symptoms I was having was that it started working, but after playing a few videos, the whole server 'hung' without any clues in logs etc, for around 5 mins or so, then started working again. After a frustrating time trying to get Plex to work under Kubernetes (using the docker plex, and Rancher kubenetes in a homelab), i have finally got it to work.