awi-ciroh: upgrade k8s to 1.25, and adjust node pools following event #2554
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Merging this PR will trigger the following deployment actions. Support and Staging deployments
Production deployments
|
yuvipanda
approved these changes
May 19, 2023
|
Thanks @yuvipanda! I didn't finish the PR description in time for your review, but there is now one :) |
|
🎉🎉🎉🎉 Monitor the deployment of the hubs here 👉 https://github.com/2i2c-org/infrastructure/actions/runs/5022001886 |
14 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prepared for node sharing
The awi-ciroh cluster had a workshop where we ran into limitations from using 1:1 user:node. Due to that we did a behind the scenes quick migration to a node sharing setup.
This node sharing setup is now complemented, allowing us to reconfigure the awi-ciroh hubs without further terraform changes based on their wishes.
K8s cluster upgrade
I made an opportunistic upgrade of the k8s cluster while adjusting node pools. I also gained some experience which helps create GKE k8s cluster upgrade docs. Those notes are captured and linked from #2157.
Future work
They now have a UI with small / medium / large / huge, but they will just start on the n2-highmem-16 machine no matter what with a pod requesting memory based on the legacy 1:1 user:node profile list options.
I'll reach out in order to align their setup to a typical node sharing setup, which from this point onwards is just a hub config change.