fhke

3 ms·

1. 1.▲
   by fhke 2y ago

   > Why did it regress into Kubernetes The “KISS solution” didn’t scale to the requirements of modern business. I remember running chef - essentially a complicated ruby script - on 100ks of servers, each of which with their own local daemo
2. 2.▲
   by fhke 2y ago

   >The high cost arises from needing to provision a bare-bones cluster with redundant management nodes. ?! How else are you managing your infrastructure besides having redundancy in the control plane? Even if it’s a chef or puppet server,
3. 3.▲
   by fhke 2y ago

   Exactly this. If they didn’t do this, us-east-1a would be the biggest single point of failure the world has ever seen.
4. 4.▲
   by fhke 2y ago

   Notwithstanding the fact that this was a user misconfiguration, S3 allows you to configure public access blocks to prevent this sort of thing.
5. 5.▲
   by fhke 2y ago

   I’m no k3s expert, but this surprised me: > I noticed that there is only one k3s node that has the control-plane,master role. If that node fails you can no longer manager the cluster. This feels like a failing of k3s that should be addre
6. 6.▲
   by fhke 3y ago

   All cloud providers provide public APIs for managing infrastructure, how is kubernetes any different? Your viewpoint operates on the assumption that a private network provides additional security in comparison to the public internet, which