Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AAW Infra: scale down gerenal nodepool #1965

Open
7 tasks
Souheil-Yazji opened this issue Sep 13, 2024 · 0 comments
Open
7 tasks

AAW Infra: scale down gerenal nodepool #1965

Souheil-Yazji opened this issue Sep 13, 2024 · 0 comments
Labels
area/engineering Requires attention from engineering: focus on foundational components or platform DevOps kind/feature New feature or request priority/soon

Comments

@Souheil-Yazji
Copy link
Contributor

Is your feature request related to a problem? Please link issue ticket

Let's look at scaling down the General Nodepool to saturate the nodes better.
Currently, with some observation using grafana/lens, I can see that we are looking at maximum utilization of ~30% for CPU/mem in terms of node resource usage.

Another issue is that most of the daemonsets that don't necessarily need to be on the general nodes do have a pod on them. This is costly at no added value.

Describe the solution you'd like

  • Investigate the resource saturation on the average general nodepool node.
  • Investigate the daemonsets which deploy to general nodes
  • Identify possible clean up for those daemonsets, we can use taints/toleration to prevent them from scheduling pods to the general nodes
  • Apply step 3
  • Collect metrics on new resource utilization
  • Adjust the size of the nodes by changing the VMSS VM type
  • Save lots of money.

Describe alternatives you've considered

NA

Additional context

image
image

@Souheil-Yazji Souheil-Yazji added kind/feature New feature or request area/engineering Requires attention from engineering: focus on foundational components or platform DevOps priority/soon labels Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/engineering Requires attention from engineering: focus on foundational components or platform DevOps kind/feature New feature or request priority/soon
Projects
None yet
Development

No branches or pull requests

1 participant