Companies have reversed unpopular decisions in the past (just saw a thing about Facebook reversing some AI thing). So there may be some possible chance of them reversing this decision. I’m not hopeful but the cost is cheap, and it has a better chance of success than doing nothing
I’m not disagreeing with your premise, but the statement about Diebold atms being flawless is not true https://www.wired.com/story/vss-atm-vulnerabilities-defcon-2024/
thanks; for anyone looking, the issues have been split out at the bottom, none of them are addressed as of this writing. I don’t know that I feel like they are that serious (most of them allow you to play things if you know an ID), but they are the kind of thing you’d see in a project where there are bigger security issues.
What security gaps in particular? I did have to reverse proxy to get it to https, are there additional security issues?
I find the clients ok, not great, but I haven’t explored that space much, there are many more options than Plex. Plex seems to be making theirs worse. It actually seems like Plex tries to make my content in their client harder to find.
The real issue is jellyfin is not as good at finding metadata. I’ve overcome this with tinymediamanager, but it still isn’t as good.
For secure remote streaming, I’ve got mine behind caddy with https (caddy does the let’s encrypt dance it’s really pleasant, even works with my free DNS provider), which seems about as secure as Plex was. Are there other security aspects I’m missing that Plex provides?
For this kind of thing i usually go by popularity (active repo/popular repo), mostly to have the most other people in your boat. It doesn’t always work but generally if other users have to migrate at least you can ask them questions.
On the face of it i’d go with the csi driver version, only because we use alternative csi drivers ourselves, and haven’t seen any issues (ours are pretty aws vanella though).
We use storage classes (for our drivers) the “dynamic provisioning” section of https://juicefs.com/docs/csi/guide/pv, you’ll need to make one of those, then create a statefulset and mount the pv in there.
I do find statefulsets to be a bit of a not as well supported part of kubernetes, but generally they work well enough.
I guess i shouldn’t have answered, I do have experience with multiple storage-classes, but none of the classes you mention (so like i don’t really know anything about them). I envisioned you dealing with pod level storage issues and thought that’d be something most programs would have lots of difficulty dealing with, where as a more service oriented approach would expect remote failures (hence the recommendation).
All of the things you mentioned don’t seem like they have provisioners, so maybe you mean your individual nodes would have these associated remote fs’. At that point i don’t think kubelet cares, you just mount those on the machines and tell kubelet about it via host mount
Oh shit look there’s a CSI driver for juicefs https://juicefs.com/docs/csi/introduction/, they kinda start out recommending the host mount https://juicefs.com/docs/cloud/use_juicefs_in_kubernetes/.
We make some use of PV’s but people i find my team often tend to avoid them.
I probably should have shut my mouth from the start!
My gut says go multi cluster (or not) at that pointbut treat the remote as a service, have a local container be a proxy
“a” has a name: regulatory capture.
Regulators have in the past fulfilled their role, they’ve just been hamstrung.