2 ms·

Funnily enough the post isn't shitting on k8s, it's shitting on cloud and that k8s (lipstick) can't fix the pig (cloud)

• aliasxneo 6mo ago
  Yeah, I meant to respond to another thread (the top one currently) that was talking more specifically about k8s-hate.
• physicles 6mo ago
  That part was really surprising to me because for the kind of compute lake he’s talking about building, k8s seems like a pretty good fit for the layer that sits just above it. We run k8s with several VMs in a couple different cloud providers. I’d love it if I could forget about the VMs entirely. Is there a simpler thing than k8s that gets you all that? Probably. But if you don’t use k8s, aren’t you doomed to reimplement half of it? Like these things: - Service discovery or ingress/routing (“what port was the auth service deployed on again?”) - Declarative configuration across the board, including for scale-out - Each service gets its own service account for interacting with external systems - Blue/green deployments, readiness checks, health checks - Strong auditing of what was deployed and mutated, when, and by whom