Yep. And if you want to really save some cash and don't mind getting a little crazy, use an EKS node orchestrator that supports spot instances. I'm starting to do a serious dive into Harness at the moment actually.

Google recently released a white paper on cost saving in kubernetes as well.

[–] CIA_chatbot@lemmy.world 1 points 1 year ago

Azure has something similar in AKS as well

[–] Toribor@corndog.social 1 points 1 year ago (2 children)

If you've got a kubernetes cluster running on 10 different spot instances, isn't there a risk that all ten could be revoked at the same time? Even if they are built out across regions and availability zones?

[–] Zalack@startrek.website 1 points 1 year ago

Counterargument: I don't need Lemmy to have 100% uptime. It's not a corporate service and while -- obviously -- if it's down all the time I would eventually move on, I'm not going to fault a not-for-profit entity for periodic failures.

[–] Phoenixbouncing@lemmy.world 1 points 1 year ago

Got my AWS architect cert 2 weeks ago.

What you can do is setup a spot fleet so it'll fill up with spots and only use on-demand if spot goes above the on demand price.

You could also have a pure spot fleet and a reserved instance and use a load balancer with health checks to route traffic.

The one thing you shouldn't do with cloud providers is lift and shift your existing instances, that's what leads to the crazy prices some people are seeing.

Renting an ec2 on demande and installing your software is almost always the wrong way to do it.