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.

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

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

Closed
10 tasks done
Tracked by #4257
yuvipanda opened this issue Jul 6, 2024 · 1 comment · Fixed by #4399
Closed
10 tasks done
Tracked by #4257

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

yuvipanda opened this issue Jul 6, 2024 · 1 comment · Fixed by #4399
Assignees

Comments

@yuvipanda
Copy link
Member

yuvipanda commented Jul 6, 2024

Once #4337 is done, time to move the rest of the hubs. Should follow the same process that is tested on the staging hub.

Tasks


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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants