clintkev251

Not that I've found. Plexamp + Sonic analysis (and everything that comes along with that) is one of the major factors that keeps me committed to Plex as my primary media server. I run Jellyfin alongside, but the music experience (as well as other things) just can't stand up to Plex yet

Change the name of the port in your service to HTTP, or explicitly set the scheme as HTTP. From the Traefik docs:

There are 3 ways to configure the backend protocol for communication between Traefik and your pods:

Setting the scheme explicitly (http/https/h2c)

Configuring the name of the kubernetes service port to start with https (https)

Setting the kubernetes service port to use port 443 (https)

If you do not configure the above, Traefik will assume an http connection.

https://doc.traefik.io/traefik/routing/providers/kubernetes-crd/#kind-traefikservice

I'm running probably 100 services in Kubernetes in my homelab, most of it is made up of manifests that I've written translated over from docker compose files where I used to run the services. I also run some helm charts, but mostly just for more complex sets of services. I commit everything to a private GitHub repository, Flux replicates it to the cluster, and Renovate handles updates. Obviously writing manifests for Kubernetes is way more complex compared to Docker, but that's kinda the point right, Kubernetes is way more powerful than Docker, so it's going to come with extra complexity to match

This is easy with Traefik. Just create one entrypoint for public services in addition to your existing entrypoint. Then point Cloudflare at your new entrypoint and add services that you intend to publicly expose to that entrypoint, then add everything else to the other entrypoint that isn't connected to Cloudflared

I say it's a necessity not from a technical standpoint (of course you can just forward random ports directly to services), but from a "doing things the right way" standpoint. Especially if you're intending to expose services which aren't expressly designed with internet exposure in mind, a reverse proxy is hugely important for security as far as implementing SSL and authentication

They way that most projects I've seen that have multiple dependencies handle this is to just provide an example docker compose file. I really think that's all you need. Personally I really don't want an "overpackaged" solution, because that just adds bloat and takes away flexibility. I don't need yet another proxy running, if I need to proxy access to some service, I'll integrate it into my existing proxy.

My method for music requests right now is "you can text me if you need something added"

Overseerr has stated that they have no plans to implement music support. It's on Jellyseerr's roadmap, so maybe it will come there at some point, I guess we'll see. Ultimately the issue is that Music is a pain to deal with and I think a lot of people don't even have music libraries, so demand is likely lower