search

eclipse-cbi / buildkitd-okd

Other
1 stars 0 forks source link

Target speed fast node and allocate more resources #2

Open heurtematte opened 8 months ago

heurtematte commented 8 months ago

I had issue with an heavy build on nodes without annotation speed:fast.

mbarbero commented 8 months ago

Fast nodes have a limited amount of memory and small CPUs. Making this change would essentially reserve 5 fast nodes for Docker builds, which seems undesirable. However, I don't have the current status of the cluster in mind, so an assessment of the number of fast nodes and their associated resources would help determine if this is reasonable or not.

heurtematte commented 8 months ago

The current status of node with labels speed:fast: 6 nodes with 8cpu and 32G of RAM.

I propose to create a new service buildkitd-fast related to a new deployment with only one pod and targetting nodes with label speed:fast. So my pipeline will be able to target this specific node. WDYT?

Would Horizontal Pod Autoscaler be interesting to set up for this infra ?

mbarbero commented 8 months ago

I had issue with an heavy build on nodes without annotation speed:fast.

Was it really about the nodes not being speed:fast, or just limitations in terms of cpu/memory? I'm asking because it seems you want both a fast node and increased resources. I suspect that increased resources alone might be sufficient. Some insights into your issues would be helpful :)