2i2c-org / infrastructure

Infrastructure for configuring and deploying our community JupyterHubs.
https://infrastructure.2i2c.org
BSD 3-Clause "New" or "Revised" License
105 stars 64 forks source link

Move remaining hubs on catalystproject-latam to new filestore #4368

Closed yuvipanda closed 4 months ago

yuvipanda commented 4 months ago

Once https://github.com/2i2c-org/infrastructure/issues/4337 is done, time to move the rest of the hubs. Should follow the same process that is tested on the staging hub.

### Tasks
- [x] cabana
- [x] cicada
- [x] gita
- [x] iner
- [x] labi
- [x] nnb-ccg
- [x] plnc
- [x] unam
- [x] unitefa-conicet
- [x] uprrp

The process here would be:

  1. Wait for a hub to have no active users
  2. Stop new users from accessing the hub (I suggest by doing a k -n <hub-name> delete svc proxy-public)
  3. Do one final rclone
  4. Deploy the change to point to the new filestore IP. This should also bring back proxy-public svc and restore access.

(4) further needs:

  1. k delete pv <hub-name>-home-nfs --wait=false
  2. k -n <hub-name> delete pvc home-nfs --wait=false
  3. k -n <hub-name> delete pod -l component=shared-dirsize-metrics
  4. k -n <hub-name> delete pod -l component=shared-volume-metrics

This is because PersistentVolumes are not editable, and we must delete and recreate them to allow the new deploy with new IP to succeed. And this is the sequence of the objects dependent on the PV, and we need to delete all these for it to finish.

sgibson91 commented 4 months ago

Mostly done, just have to wait for unitefa-conicet to empty out