Nah, use one VM on each node as the kube host. That’s fine. You’re doing it for fun, you don’t need to min-max your environment.

You’ll probably want to tear it down and redeploy it eventually anyway. That’s going to be a pain if you’ve installed them on bare metal.

So what you’re saying is there’s no reported evidence of that happening.

I don’t think jellyfin supports that either. I tried it a while back and only saw partial success.

Docker packs the whole application and its dependencies into a container, hence the name. You can run and delete that application as much as you want without affecting the host system. (But you should probably keep your media library and config outside the container, and use a bind mount. The setup documentation covers this.)

The alternative is fragmentation.

Yeah lemme just do that on my apartment

The board

Proxmox can run lxc containers natively.

Personally I keep a Debian VM for docker, a holdover from before hypervisors supported containers natively. I use docker compose and it Just Works™.

I don’t think jellyfin runs on DOS.

VPN. Jellyfin is not intended for direct exposure to the Internet.

You should run it in docker anyway for convenience. A reverse proxy is optional, but I use traefik also for convenience (so that I can just use domain names on the same port, and so that it can automatically fetch certs).

And most of them are shit at their jobs because they just do it for money. No care for the skill.

That’s just called Access

Intel’s current corporate nonsense doesn’t affect the quality of existing products. They will continue to be supported under Linux and BSD for a long time.