Any way to "take over" an existing server?

[mcronce]

This is more of a question than an issue, but I'll make a PR to the docs based on the answer if it'll help :)

I've got a Plex server already, which I've migrated through all the iterations of my homelab over the past few years - which, as of today, isn't single-node Kubernetes anymore.

I'd like to retain that Plex server's database and migrate to kube-plex to take advantage of the elastic transcoding, but don't want to have to make a "new" server. The README instructs to grab a claim token and spin up a server.

Is there any way to utilize the existing server's database and not provide a new claim token? If not, would copying Plex's DB in after creating it cause any issues with the changed claim token?

[cheeragpatel]

Plex stores all the db info on the file system, if you mount that directory to the container it should just think its the old plex server. I'm currently running plex in docker and /config mount is what you need:

/srv/app-data/plexmediaserver:/config

Where the first arg is the local disk and /config is the mount on the container.

The token is just for plexpass updates, you can have a different one and it won't matter as far as the plex server is concerned.

[ccomarato]

I have a similar question. I have an existing Plex server that I have configured on Windows that is working exactly the way I want it to; however, I'd love the ability to offload transcode jobs to a Kubernetes cluster. Is there any way to plugin a shim like this on an existing Plex server installation and leverage kube-plex or something similar for the elastic transcoding without having to provision an entirely new containerized Plex server?