fix(jupyterhub): updated admin and increases disk size

[vevetron]

Description

Updates admins and increases disk size for new jupyterhub images.

Resolves #3421

Type of change

• [x] Bug fix (non-breaking change which fixes an issue)

How has this been tested?

YOLO (I really don't know how)

Post-merge follow-ups

Document any actions that must be taken post-merge to deploy or otherwise implement the changes in this PR (for example, running a full refresh of some incremental model in dbt). If these actions will take more than a few hours after the merge or if they will be completed by someone other than the PR author, please create a dedicated follow-up issue and link it here to track resolution.

• [ ] No action required
• [x] Actions required (specified below) Check if default disk sizes are updated with df -h Currently it looks like:

  jovyan@jupyter-vevetron:~/data-analyses$ df -h
  Filesystem      Size  Used Avail Use% Mounted on
  overlay          95G   17G   78G  18% /
  tmpfs            64M     0   64M   0% /dev
  tmpfs           7.9G     0  7.9G   0% /sys/fs/cgroup
  /dev/sdc        9.8G  6.7G  3.2G  68% /home/jovyan
  /dev/sda1        95G   17G   78G  18% /etc/hosts
  shm              64M     0   64M   0% /dev/shm
  tmpfs           7.9G     0  7.9G   0% /proc/acpi
  tmpfs           7.9G     0  7.9G   0% /proc/scsi
  tmpfs           7.9G     0  7.9G   0% /sys/firmware

[github-actions[bot]]

The following changes will be applied to the production Kubernetes cluster upon merge.

BE AWARE this may not reveal changes that have been manually applied to the cluster getting undone—applying manual changes to the cluster should be avoided.

jupyterhub, hub, Deployment (apps) has changed:
...
          hub.jupyter.org/network-access-proxy-api: "true"
          hub.jupyter.org/network-access-proxy-http: "true"
          hub.jupyter.org/network-access-singleuser: "true"
        annotations:
          checksum/config-map: ecf5268b9d342e8ab7c99ede7cbfde395133c574e9a4b24e25c2e825968e8311
-         checksum/secret: 309ff02a3b9f4c1db840a2bdd1b283b4ae31ccd8e090e18f37364dae1512623b
+         checksum/secret: 48404a3a5a831ce46ea2e2805be9b8b0fe6079f20847583ebcba69d45de0f715
      spec:
        tolerations:
          - effect: NoSchedule
            key: hub.jupyter.org/dedicated
            operator: Equal
...
jupyterhub, hub, Secret (v1) has changed:
...
    name: hub
  data:
    hub.config.ConfigurableHTTPProxy.auth_token: 'REDACTED # (64 bytes)'
    hub.config.CryptKeeper.keys: 'REDACTED # (64 bytes)'
    hub.config.JupyterHub.cookie_secret: 'REDACTED # (64 bytes)'
-   values.yaml: '-------- # (11158 bytes)'
+   values.yaml: '++++++++ # (11192 bytes)'
  type: Opaque

[vevetron]

So after merging in and running github actions, I logged out and stopped my server. My admin rights changed. But I don’t see my disk size changed.

Went to Lens -> Cluster -> Storage -> PVC, Updates Spec -> Storage to 100gb to match Edmasklies Now my server df -h matches with 100gb of storage

Side note: Deleted PVC of walteryu, now i'm spinning up his server again. His old volume disappeared, his new volume is 32gb, which matches our config.

I'm not sure if his files disappeared or he didn't have anything to being with.

I gave him some files and then shut down his server and then deleted his pvc, then had him start up again. His files were gone, he got a new PV.

Thus I think it makes the most sense just to manually increase the PV size in PVC of existing users (Andrew knew this). Then any new user will have 32 gigs of storage.