Procedure to destroy old notebook volumes

[ca-scribner]

Every notebook server by default creates a volume. Users can optionally create additional persistent volumes at notebook creation. These are not destroyed at notebook termination.

Possible solutions:

• do we care? If we don't mind having these persist indefinitely, close this :)
• do we have an existing way for users to cull these.
  • If yes: add it to docs for storage
  • If no: should we?
• do we have automated garbage detection for the system to notice when users aren't culling these themselves?

[blairdrummond]

My thinking is that we probably need to create a good notification system somehow. Have an automated culling policy (that's super easy I think), and give users a 30,15,1 day heads-up before their pvcs get culled, unless they attach the PVCs.

[blairdrummond]

We can probably revisit this (eventually) now that we have a notification system in place from the Orchard folks. We can send warning emails well in advance.

[brendangadd]

As a user, I want to see all my notebook volumes and delete the ones I don't need.

Let's add UI to the Jupyter web app component of Kubeflow to enable listing and deletion of persistent volumes.

• List all of (and only) the volumes owned by the user
• Only allow deletion of volumes that are not in use – probably equivalent PVC not being mounted

The logic for displaying volumes and allowing deletion is probably similar to that which displays the list of existing volumes available to be attached to a new notebook server.

Edit: Shouldn't have to work with PVs themselves, but rather the associated PVCs. I think these PVs are automatically cleaned up when there is no bound PVC.

/cc @wg102