Skip to content

Conversation

RoshaniN
Copy link
Collaborator

Fixes / Features

This feature only affects Pathways enabled clusters.

  • Workloads are bottlenecked by the number of CPU nodes on clusters with Pathways enabled.
  • Increasing the default number of CPU nodes to 4 (which was 1 previously).
  • Making this change backward compatible by resizing the Pathways CPU nodepool, if the cluster is already Pathways enabled.

Testing / Documentation

Tested on a cluster with 19 v5litepod-32

  • [ y/n ] Tests pass
  • [ y/n ] Appropriate changes to documentation are included in the PR

@RoshaniN RoshaniN requested a review from shauryagup May 28, 2025 21:22
@RoshaniN RoshaniN added enhancement New feature or request release-bugfix and removed enhancement New feature or request labels May 28, 2025
@RoshaniN RoshaniN force-pushed the increase_nodepools branch from 2edb313 to f9fefa6 Compare May 28, 2025 21:55
@RoshaniN RoshaniN force-pushed the increase_nodepools branch from f9fefa6 to eac6490 Compare May 28, 2025 22:15
f' --machine-type={args.pathways_gce_machine_type} --scopes=storage-full,gke-default,{CLOUD_PLATFORM_AUTH_SCOPE_URL} --enable-autoscaling'
' --min-nodes=1 --max-nodes=20'
)
# Resize Pathways CPU nodepool to have at least 4 nodes
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, however I believe it will downsize a node-pool if the number of nodes are already bigger than 4 nodes.

@pawloch00
Copy link
Collaborator

@RoshaniN is this going to be merged?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants