Bump hub version to 0.11

[GeorgianaElena]

Closes #82

[GeorgianaElena]

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]

@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]

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]

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

[yuvipanda]

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

[jsg-uoft]

@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]

@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]

@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]

@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]

@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]

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]

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

[consideRatio]

This LGTM!

Note on the imagePullSecret section, create and enabled are both set but you should only need one as they are aliases. But, due to a bug in 0.11.1 you should use .create rather than .enabled if one is chosen.

[jsg-uoft]

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

[yuvipanda]

This is great! Thanks :)

[GeorgianaElena]

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