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.

Sign up for GitHub

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

Jump to bottom

Migrate existing GCP GKE based hubs from k8s 1.22+ to 1.24+ #2157

Closed
13 of 14 tasks
consideRatio opened this issue Feb 7, 2023 · 2 comments
Closed
13 of 14 tasks

Migrate existing GCP GKE based hubs from k8s 1.22+ to 1.24+ #2157

consideRatio opened this issue Feb 7, 2023 · 2 comments
Assignees
@consideRatio

Comments

@consideRatio
Copy link
Contributor

consideRatio commented Feb 7, 2023 •
edited
Loading

This is the current status of GCP GKE clusters. We should get them all to 1.24+. This is where the "regular" release channel of GKE is currently at.

Action points

Related
@consideRatio consideRatio mentioned this issue Feb 7, 2023
Closed
10 tasks
This was referenced Feb 7, 2023
Closed
Closed
@damianavila damianavila moved this from In progress to Ready to work in DEPRECATED Engineering and Product Backlog Feb 15, 2023
@damianavila damianavila moved this to Todo 👍 in Sprint Board Mar 2, 2023
@consideRatio consideRatio mentioned this issue Mar 2, 2023
Closed
3 tasks
@consideRatio consideRatio mentioned this issue May 19, 2023
Merged
yuvipanda added a commit to yuvipanda/pilot-hubs that referenced this issue Jun 9, 2023
@yuvipanda
Change memory guarantees for meom-ige hub
4b2ae7f 
We upgraded k8s versions, and it looks like the new
nodes reserve more memory for system pods.

Ref 2i2c-org#2157
@yuvipanda
Copy link
Member

I made a table with all our versions, after opportunistic updates to meom-ige, 2i2c and cloudbank:

cluster control plane version nodes version
nasa-cryo v1.25.9 v1.25.6
carbonplan v1.24.13 v1.24.7
gridsst v1.25.9 v1.25.6
jupyter-meets-the-earth v1.25.9 v1.25.7
pangeo-hubs v1.24.12 v1.20.8,v1.21.11
awi-ciroh v1.25.8 v1.25.6
meom-ige v1.26.4 v1.26.4
utoronto v1.26.3 v1.26.3
m2lines v1.24.12 v1.24.5
victor v1.25.9 v1.25.6
2i2c v1.26.4 v1.26.4,v1.24.11
linked-earth v1.24.12 v1.24.7
openscapes v1.24.13 v1.24.9
qcl v1.24.12 v1.24.9
2i2c-aws-us v1.25.9 v1.25.6
2i2c-uk v1.24.12 v1.24.5
ubc-eoas v1.24.13 v1.24.7
cloudbank v1.26.4 v1.26.4
callysto v1.25.8 v1.25.6
smithsonian v1.25.9 v1.25.7
leap v1.25.8 v1.25.6
nasa-veda v1.25.9 v1.25.6

Looks like pangeo-hubs is the only one that's <1.24

@yuvipanda yuvipanda mentioned this issue Jun 9, 2023
Merged
@consideRatio consideRatio changed the title Migrate existing GCP GKE based hubs from k8s 1.22+ to 1.24+ Document procedure and migrate existing GCP GKE based hubs from k8s 1.22+ to 1.24+ Jun 9, 2023
@damianavila damianavila moved this from Ready to work to In progress in DEPRECATED Engineering and Product Backlog Jun 10, 2023
@damianavila damianavila moved this from Todo 👍 to In Progress ⚡ in Sprint Board Jun 10, 2023
@yuvipanda yuvipanda mentioned this issue Jun 24, 2023
Closed
3 tasks
@consideRatio consideRatio mentioned this issue Jul 7, 2023
Merged
@consideRatio
Copy link
Contributor Author

Closing this as completed, and extracting out the part about documenting the upgrade procedure.

@consideRatio consideRatio changed the title Document procedure and migrate existing GCP GKE based hubs from k8s 1.22+ to 1.24+ ;igrate existing GCP GKE based hubs from k8s 1.22+ to 1.24+ Oct 10, 2023
@consideRatio consideRatio changed the title ;igrate existing GCP GKE based hubs from k8s 1.22+ to 1.24+ Migrate existing GCP GKE based hubs from k8s 1.22+ to 1.24+ Oct 10, 2023
@consideRatio consideRatio mentioned this issue Oct 10, 2023
Open
3 tasks
@damianavila damianavila moved this to Done 🎉 in Sprint Board Oct 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@consideRatio consideRatio

Labels
None yet
Projects
No open projects
DEPRECATED Engineering and Product Backlog
Status: Complete
Sprint Board
Archived in project
Milestone
No milestone
Development

No branches or pull requests
2 participants
@yuvipanda @consideRatio