community-edition VS LocalStack

"They have even abandoned their Tanzu community edition." https://tanzucommunityedition.io/

Actually it is free for non-commercial use in a vSphere env up to 100 cores. For public cloud I have no idea how do they count the licenses/cores but you can give a shoot with the TKG. The TKG replaces the TCE. https://tanzucommunityedition.io

You choose to run production workloads on the community edition?

e.g. https://tanzucommunityedition.io/ has some opinions about how to set things up but there's no support contract, so I'd view it as providing guidance or defaults that are likely to work for most use-cases, similar to "I want to make a web app but i'm not already an expert with years of production experience, so i'll use a framework like django/rails/spring/etc. instead of writing free-form from scratch"

Tanzu Community Edition (https://tanzucommunityedition.io/) with "unmanaged clusters" is a fully free + OSS solution for using the cluster and package management tools of vmware's Tanzu without being locked in to other parts of the vmware stack. I honestly don't know all the details but there's a way of buying a support contract also.

You can check out TCE https://tanzucommunityedition.io/ This helps to setup in a single click with UI based deployment

Making its cluster available for many flavors through its Community Edition called TCE (Tanzu Community Edition)

Might I sugest Tanzu? https://tanzucommunityedition.io/

Tanzu Community Edition also supports vSphere/AWS - https://tanzucommunityedition.io/

Hey vnadkarni! Would be great for you to join the community on the Kubernetes Slack. Questions can also be posted in the GitHub Issues or Discussions.

Later you can use any S3 compatible storage because the code I write will still work, but for testing purposes on my local machine, I will use LocalStack:

Acesse o site da LocalStack e faça login.

To give this a slightly different spin:

--> "The best optimization is simply not spinning things up."

At least for local development and testing, as made possible by LocalStack (https://localstack.cloud), among other local testing solutions and emulators.

We've seen so many teams fall into the trap of "someone forgot to shut down dev resource X for a week and now we've racked up a $$$ bill on AWS".

What is everyone's strategy to avoid this kind of situation? Tools like `aws-nuke` (https://github.com/rebuy-de/aws-nuke) are awesome (!) to clean up unused resources, but frankly they should not be necessary in the first place.

(For others who hadn't heard of it: localstack is

LocalStack Website

O Localstack: https://localstack.cloud/, é um recurso que possibilita simular diversos recursos AWS (dynamoDB, s3, iam, cognito, ses), dentro da sua máquina, utilizando o docker.