terraform-provider-multy VS autoscaler

You can use it through a Terraform provider right now. If you're interested, you can get an API key at https://multy.dev, we'd love to get some feedback!

No problem. I'm also quite familiar with implementing a terraform provider so let me know if you need help around that or you can take some examples from https://github.com/multycloud/terraform-provider-multy

Our main repository is https://github.com/multycloud/multy and we also have a terraform provider at https://github.com/multycloud/terraform-provider-multy.

Thanks for reading the post, I’ve really come to prefer the type safety of protobufs and gRPC and it’s made developing Multy all the easier. If you want to look at a real world example of gRPC, take a look at the Multy engine running the gRPC server and a client example in our terraform provider.

Take a look at multy.dev and let us know what you think! Specifically our kubernetes cluster resource might be interesting for you: https://registry.terraform.io/providers/multycloud/multy/latest/docs/resources/kubernetes_cluster

We have a discord channel where we're starting to build a community of developers. Our two main repos are the engine and our Terraform provider. Have a browse and tells us what you think!

Me and a few friends have been working on multy.dev, an open-source[1] cloud agnostic API that makes it easy to deploy the same infrastructure to any cloud provider using native managed services.

We use Cluster Autoscaler to automatically adjust the number of nodes (cluster size) based on your actual usage to ensure efficiency. Additionally, we deploy Vertical and Horizontal Pod Autoscalers to scale your applications' resources as their needs change automatically.

> * Hetzner: cheap, good service, the finest pets in the world, no cattle

You can absolutely do cattle with Hetzner. They support imaging and immutable infrastructure. They don't have a native auto scaling equivalent, but if you're using Kubernetes, they have a cluster autoscaler: https://github.com/kubernetes/autoscaler/blob/master/cluster...

Here we take the VPA as a starting point to analyze the design and implementation principles of the VPA in Autoscaler. The source code for this article is based on Autoscaler HEAD fbe25e1.

Autoscaling over EKS can be accomplished using either the cluster-autoscaler project or Karpenter. If you want to use Spot instances, consider using Karpenter, as it has better integrations with AWS for optimizing spot pricing and availability, minimizing interruptions, and falling back to on-demand nodes if no spot instances are available.

Autoscaling is already provided on OVH, but we don't use it for now. Autoscaler has to be manually installed on the AWS/EKS cluster.

do you mean this: https://github.com/kubernetes/autoscaler/blob/master/vertical-pod-autoscaler/pkg/recommender/README.md

Read more about this scaler in detail here!

We have a default node group of Linux hosts, but there's a secondary nodegroup of Windows hosts that is typically scaled down to 0. When a team's build runs, a pod is scheduled based on their definition. Cluster-autoscaler will check the nodeSelector and automatically spin up a node from that nodegroup if necessary.

I am running a Kubernetes cluster(AWS EKS one) with Autoscaler pod So that Cluster will autoscale according to the resource request within the cluster.