iso,

yeah, you pretty much described the use case for k8s. It allows for rapid horizontal scaling, since you can easily throw another machine into the cluster if you need it. It mostly makes sense if you actually have multiple machines sitting idle to begin with, so this technology is mostly used in combination with managed quick rent servers (think AWS).

Beyond that, k8s is kinda fancy for cluster management, but if you don’t have a cluster you kinda don’t need it to begin with. Using simple kernel VMs (think Proxmox) or just Docker works better there. You could still go for k8s since it’s pretty much docker with cluster functionalities, just in case you want to expand eventually (sidenote, docker allows for cluster functionalities too, but they put a price on it, while k8s is open source iirc).

In that company I worked, k8s was considered but ultimately not implemented since it was considered a bit overkill. We already had everything set up with a bunch of bash scripts anyway, so it didn’t matter too greatly to begin with.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • main@lemmy.blahaj.zone
  • kavyap
  • thenastyranch
  • ethstaker
  • osvaldo12
  • mdbf
  • DreamBathrooms
  • InstantRegret
  • magazineikmin
  • Youngstown
  • khanakhh
  • Durango
  • slotface
  • rosin
  • cubers
  • JUstTest
  • everett
  • cisconetworking
  • tacticalgear
  • ngwrru68w68
  • Leos
  • GTA5RPClips
  • normalnudes
  • modclub
  • tester
  • anitta
  • megavids
  • provamag3
  • lostlight
  • All magazines