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
Decide your budget first, everything after that follows. Most likely like others have said ignore that old pc, you get get something much better second hand for very cheap.
It seems like your ignoring that this will encourage tipping, that has tended to lower wages, as seen in USA. It doesn't seem like this is perfect or good
Miller and Valasek’s full arsenal includes functions that at lower speeds fully kill the engine, abruptly engage the brakes, or disable them altogether. The most disturbing maneuver came when they cut the Jeep's brakes, leaving me frantically pumping the pedal as the 2-ton SUV slid uncontrollably into a ditch.
I feel like they def have issues, Taiwan, Tibet, Uyghurs, human rights record, general authoritarianism.
They also seem to have a better climate change story than anyone in north america, and USA has totally shown itself to be a mercurial alley.
I don't see what advantage high tariffs have on something we want more of (EV's). If the standards suck, then I'm ok with bringing them up to standard and charging for that.
Making this an either or "they are or aren't our enemies" seems unnecessary, when we could buy their things and put pressure on them to do better on the things at the top.
When you include non-profit housing built by others with federal government help, it's more like 3,742 houses.
But it's hard for Poilievre to take responsibility for the 200,000 homes he says were built when he was minister. In the 2015-16 fiscal year, 194,461 homes were built in Canada in total, including by private developers.
Poilievre pushed back at Singh for not letting him answer the question and insisted that 200,000 homes were built during his ministerial tenure.
Both figures aren't entirely accurate. Singh's claim that Poilievre only built six homes as housing minister refers only to non-profit community housing units built exclusively by the government in 2015. When you include non-profit housing built by others with federal government help, it's more like 3,742 houses.
But it's hard for Poilievre to take responsibility for the 200,000 homes he says were built when he was minister. In the 2015-16 fiscal year, 194,461 homes were built in Canada in total, including by private developers.
I think it's important to reward people who save for retirement. I agree that you've got to have something before you can save. IMO taxing high wealth i.e. top 5% of the population higher rates so that you can fund the bottom 10% would go a long way to making sure things are a bit more balanced, while still rewarding your "hardest" (which are probably actually your luckiest) workers.
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.