Hey there! :wave: I’m currently looking at our AWS costs as they seem very high to me for our workload – happy to give more details in private. On the EKS side, our nodes seem under utilized to me, at least in term of usage (~10% CPU / RAM avg). So I tried to scale down the cluster: I lowered th…

Hello ! I’ll try to answer step by step. First, the major control plane is actually Qovery, every modification done cloud provider side will be override by Qovery. This time it’s ok but careful, a wrong manipulation provider side could lead to break your cluster or the link with the Qovery control…

it could be great for me aswel to test this :smiley:

TL;DR: I still don’t know why my cluster didn’t scale down by itself earlier, but at least I do know now that it can’t scale down more than it did yesterday because all nodes have a high CPU allocation. [image] Enzo: The best way is to let the autoscaler do the job. For your information, the sc…

Hey there! We just updated our cluster to switch to bigger instances. The move was super smooth, thanks and congrats! :tada: That being said, my goal was to lower the number of instances since we now have twice more CPU and RAM. But right now the cluster is stuck with 4 instances. I’ve checked the…

Hello, what I can already say is that a part resources are allocated to applications which manage the cluster (logs, auto-scaling, networking, metrics scraping…) and allocation are already optimized as much as we can. The thing is allocation isn’t usage. If we reduce allocation of an app consuming…

I know what’s allocation and usage, and I know that you’ve already worked on reducing the overhead. :slight_smile: My point is that the current setup seems too gentle. I didn’t look at all the configurations but the scheduler doesn’t seem to binpack, there doesn’t seem to be any rebalancing mechani…

Allocated resources are used for scaling not requested ones. If we take a look at your cluster and allocated resources: Node 1: 99% CPU, 42% RAM Node 2: 78% CPU, 26% RAM Node 3: 41% CPU, 21% RAM Node 4: 92% CPU, 98% RAM That’s why it doesn’t scale down.

I thought cluster-autoscaler was only considering the requests (which AFAIK is true for the utilization threshold that triggers a scale down) but indeed, the target nodes do need to have enough allocatable space or the pods can’t be moved, thanks for the reminder. :slight_smile: What’s the rational…

What's the recommended way to scale down a cluster?

Questions and Answers

rophilogene (Romaric Philogene) June 8, 2022, 2:08pm 3

Hi @ramnes , plus I would add, maybe Qovery AWS EC2 would be a better and most cost-effective solution for you? (we don’t recommend it for production workload since it’s not resilient, but if EKS costs is an issue, it could be a good one)

Topic		Replies	Views
EKS Node autoscaling (down) AWS qovery	5	1231	September 2, 2022
EC2 Instances cluster AWS AWS qovery , aws-ec2 , aws	2	467	March 25, 2024
How Kubernetes CPU and RAM resources allocation works with Qovery? Deployment aws	18	4640	September 15, 2022
Auto-scaling with multiple apps Questions and Answers aws	16	616	February 15, 2024
AWS Cluster scaling issue - how does it work? Questions and Answers qovery , aws	3	584	March 25, 2024

What's the recommended way to scale down a cluster?

Related topics