Object storage (the S3 API stuff) is the most logical answer here, it’s much simpler and thus more reliable than solutions like Gluster, and the abstraction actually matches your use case. Otherwise something like an NFS share from a central fileserver works too.

But I agree with the other comment that you’re trying to do kubernetes on hard mode and most likely with a worse result.

Not sure what you have against minimum wage, it works well in other countries (I’m from the Netherlands). Obviously it doesn’t solve everything by itself, but it’s definitely a valuable part of a range of measures to treat people fairly. It’s a fantasy that everyone can be educated to a level above minimum wage.

That’s not true, “regular” Li-ion batteries have become tremendously cheaper and have increased their capacity by a lot in the past decade. The next jump in their capacity is about 50% more again, and it’s already being previewed by the big battery manufacturers. They’re not going to be cheap though.

Oh I agree with your post, but I was responding to Valmond who used different criteria.

You can have all three of those, but you won’t get great performance. The Samsung QVO SATA drives are a great example. I wouldn’t use those for an OS drive but they’re fantastic for NAS or media use.

If everything went fine during production you’re probably right. But there have definitely been batches of hard disks with production flaws which caused all drives from that batch to fail in a similar way.