They should not be worried, they should be educated.

If you worry a new user enough they’ll go back to Windows or Apple because there’s less scary warnings there.

We need to make the transition as pain free as possible. Learning about the joys of kernel compilation and SELinux can come later.
The first step is "Hey, this is as usable as Windows, without stupid ads in the start menu.

Sounds quite similar to Markov chains which made me think of this story:

https://thedailywtf.com/articles/the-automated-curse-generator

Still gets a snort out of me every time Markov chains are mentioned.

Coconut at least…

Ah, you “work” in “marketing”?

It doesn’t. It carries you by having a module for absolutely everything even shooting yourself in the foot.

B stands for Billion (Parameters) IIRC

No, No, they don’t understand everything and nothing!

I’m hopeful that reencoding on the fly or even merging preencoded files into a single stream is too expensive because it needs a lot of compute power and invalidates caches .

IT changes usually affect management as well, while “cost saving” in production doesn’t.

Stopping AWS instances would be handy, but your idea to slag the drives is unnecessary.

Just set up full disk encryption for everything.

You die -> no key -> no data

I run a 2 node k3s cluster. There are a few small advantages over docker swarm, built-in network policies to lock down my VPN/Torrent pod being the main one.

Other than that writing kubernetes yaml files is a lot more verbose than docker-compose. Helm does make it bearable, though.

Due to real-life my migration to the cluster is real slow, but the goal is to move all my services over.

It’s not “better” than compose but I like it and it’s nice to have worked with it.