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

Curvenote: increase nodesize to r6a.4xlarge, upgrade K8s to 1.29 #2940

Merged
merged 6 commits into from
Mar 5, 2024

Conversation

manics
Copy link
Member

@manics manics commented Mar 4, 2024

@stevejpurves has enough AWS credits to double capacity until the end of the year.

Doubling the node size from r6a.2xlarge (8 cpu, 64 memory) to r6a.4xlarge (16 cpu, 128 memory) is more efficient than doubling the number of nodes because the maximum number of EKS pods on r6a.2xlarge is 58, whereas with r6a.4xlarge it's 234. Currently nearly half the total pod capacity is taken up by system, BinderHub, and other non-user pods.

This also upgrades K8s to 1.28 (though we could also go to 1.29 https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html#available-versions - might try that since it means we won't have to upgrade again in 2024).

@manics
Copy link
Member Author

manics commented Mar 4, 2024

One of the nodes has coincidentally run out of disk space, so I might as well try the upgrade now.

@manics manics marked this pull request as ready for review March 5, 2024 10:55
@manics manics changed the title Curvenote: increase nodesize, upgrade K8s to 1.28 Curvenote: increase nodesize to r6a.4xlarge, upgrade K8s to 1.29 Mar 5, 2024
@manics
Copy link
Member Author

manics commented Mar 5, 2024

Done!

@manics manics merged commit da5d90b into jupyterhub:main Mar 5, 2024
3 checks passed
@manics manics deleted the curvenote-increase-nodesize branch March 5, 2024 11:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant