Bump hub version to 0.11

utoronto-2i2c / jupyterhub-deploy

Demo JupyterHub deployment for University of Toronto

BSD 3-Clause "New" or "Revised" License

3 stars 4 forks source link

Bump hub version to 0.11 #83

Closed GeorgianaElena closed 3 years ago

GeorgianaElena commented 3 years ago

Closes https://github.com/utoronto-2i2c/jupyterhub-deploy/issues/82

GeorgianaElena commented 3 years ago

I'm getting the following error when trying to deploy this to staging :(

Error: UPGRADE FAILED: cannot patch "hub-db-dir" with kind PersistentVolumeClaim: PersistentVolumeClaim "hub-db-dir" is invalid: spec: Forbidden: is immutable after creation except resources.requests for bound claims

@consideratio or @yuvipanda, do you know what might be going on?

yuvipanda commented 3 years ago

@GeorgianaElena oh, hmm - interesting! This looks like it's trying to change the size of the hub-db PVC, not sure why. Can you check what the current size is and see what we're asking it to be?

GeorgianaElena commented 3 years ago

It looks like the current size is 1Gi for the staging hub and 10Gi for the prod one.

The prod one has its size configured here, but the staging one doesn't, or at least I don't find it. Maybe the default size has changed and we should be explicit that we still want the 1Gi?

Update: Being explicit about its size, doesn't do any difference :(

GeorgianaElena commented 3 years ago

Thanks to a recent discussion on Gitter, I managed to get the deployment to pass by specifying the storageClassName :heart: wieee :heart:

yuvipanda commented 3 years ago

@GeorgianaElena awesome! Let's wait until Toronto is asleep before we deploy to prod? Feel free to test on staging though :)

jsg-uoft commented 3 years ago

@GeorgianaElena if you can let me know when you want to push the change (as well as duration although I imagine it's more or less instant) I can put up a service notice. Just good to have in case there are any night owls interacting with the system at the same time.

yuvipanda commented 3 years ago

@jsg-uoft makes sense! It's pretty instant, but it's big enough that a service notice seems appropriate. Where would it be made visible?

jsg-uoft commented 3 years ago

@yuvipanda we'd post it to https://www.systemstatus.utoronto.ca/ and then advertise the link to the community for awareness. It may introduce a good conversation about feature changes (if any) as well!

GeorgianaElena commented 3 years ago

@jsg-uoft I was thinking about pushing the change at around 4am Toronto time. I could set and alarm if this needs to be precise.

@yuvipanda, the error I got before, was actually because of me messing with the config. I have now fixed it.

yuvipanda commented 3 years ago

@yuvipanda we'd post it to systemstatus.utoronto.ca and then advertise the link to the community for awareness. It may introduce a good conversation about feature changes (if any) as well!

Makes sense! This shouldn't have any user facing changes I think. Thanks for being on top of it!

jsg-uoft commented 3 years ago

Thanks @GeorgianaElena I will post an announcement then for 4:00 a.m. Thurs. Feb. 18th (Eastern) and put a pointer to it into Teams. I'll just provide the bare bones info, so if you or @yuvipanda can monitor for questions that would be great!

yuvipanda commented 3 years ago

@jsg-uoft awesome. Just make sure it says we don't expect disruption nor new features :)

jsg-uoft commented 3 years ago

@yuvipanda @GeorgianaElena that's it posted. Please drop me a line if you have any feedback, thanks!

yuvipanda commented 3 years ago

This is great! Thanks :)

GeorgianaElena commented 3 years ago

This has now been deployed to both staging and prod :tada: Merging it now.