4 ms·

Not really. You didn't factor in the time it takes to manage k3s yourself versus GKE which is managed.

unixhero 3y ago
Maybe it is a very simple setuo
CactusBlue 3y ago
Probably. But it was only a single command to get up a k3s node - not much difference in effort for a relatively low-workload, low-critical service.
- threeseed 3y ago
  It's probably only a few clicks to get a GKE cluster. The point is that it's not really a fair comparison.
jitl 3y ago
Self management could be expensive if it’s actually going to burn hours of dev time. At teensy scale is k3s really gonna take much “management” after the bring-up? I don’t think so. For a teensy team, it seems totally worth it to take a runway from 12 months to 40 months for the price of a few afternoon’s work.
- CactusBlue 3y ago
  This. Just upgrading this made me (a fresh university grad with minimum savings) basically and my startup "default alive" so that the startup can be bootstrapped
- jauntywundrkind 3y ago
  The wins here are absurd, & the resistance to them remains as staunchly resolutely inconsiderate as ever. I've done Lets Encrypt by hand. I've had rotation not work as expected. I've done postgres by hand. I've spent work weeks setting up and testing backups. I've dealt with fallout from another person's backups scripts not working. I've worked with teams that took weeks to setup replicas. I've been on teams that have spent quarters building and improving ci/cd systems. Folks will never ever shut up about how you might not need Kubernetes, but damn this post documented an extremely short path through a couple kind of annoying to DIY things that just bloody work and at a much much much higher level of productization than the bullshit bespoke scripts your own team would put together. Traeffik load balancer with l7 routing? Already running. Let's Encrypt? Works, reliably. Internal DNS? Out of the box. Postgres? Incredibly well managed. Ci/cd? A nearly Heroku like beautiful world of gitops. These pieces all snap in to the general framing with ease & grace; this whole post is a complete DIY infrastructure stack that one could do in an afternoon, and even better the output is predictable & understandable & legible by another practitioner, which the "real men just do it themselves" attitude doesn't cover. The bullshit asymetry principle feels soooo strong here. Spreading fear uncertainty & doubt, yucking people's yum, is going to waste an incredible amount of time.
papichulo2023 3y ago
Dont you have it out of the box with some distros?

Maybe it is a very simple setuo

Probably. But it was only a single command to get up a k3s node - not much difference in effort for a relatively low-workload, low-critical service.

threeseed 3y ago
It's probably only a few clicks to get a GKE cluster. The point is that it's not really a fair comparison.

jitl 3y ago

Self management could be expensive if it’s actually going to burn hours of dev time. At teensy scale is k3s really gonna take much “management” after the bring-up? I don’t think so. For a teensy team, it seems totally worth it to take a runway from 12 months to 40 months for the price of a few afternoon’s work.

CactusBlue 3y ago
This. Just upgrading this made me (a fresh university grad with minimum savings) basically and my startup "default alive" so that the startup can be bootstrapped
jauntywundrkind 3y ago
The wins here are absurd, & the resistance to them remains as staunchly resolutely inconsiderate as ever. I've done Lets Encrypt by hand. I've had rotation not work as expected. I've done postgres by hand. I've spent work weeks setting up and testing backups. I've dealt with fallout from another person's backups scripts not working. I've worked with teams that took weeks to setup replicas. I've been on teams that have spent quarters building and improving ci/cd systems. Folks will never ever shut up about how you might not need Kubernetes, but damn this post documented an extremely short path through a couple kind of annoying to DIY things that just bloody work and at a much much much higher level of productization than the bullshit bespoke scripts your own team would put together. Traeffik load balancer with l7 routing? Already running. Let's Encrypt? Works, reliably. Internal DNS? Out of the box. Postgres? Incredibly well managed. Ci/cd? A nearly Heroku like beautiful world of gitops. These pieces all snap in to the general framing with ease & grace; this whole post is a complete DIY infrastructure stack that one could do in an afternoon, and even better the output is predictable & understandable & legible by another practitioner, which the "real men just do it themselves" attitude doesn't cover. The bullshit asymetry principle feels soooo strong here. Spreading fear uncertainty & doubt, yucking people's yum, is going to waste an incredible amount of time.

papichulo2023 3y ago

Dont you have it out of the box with some distros?