2i2c/climatematch: disable hook prePuller, the configurator is active…

…ly used

The case to use hook image puller with climatematch's dedicated node
pool with 256GB of memory fitting ~25 users is for when an image update
is made when multiple node pools are in use. During the last 90 days, no
more than one node pool has been used. To enable hook prePuller isn't
justified in this case I think. The configurator is likely relevant to
them as well, and a policy is in place to not allow that to be enabled
next to the hook prePuller.

config/clusters/2i2c/climatematch.values.yaml

@@ -1,9 +1,4 @@
 jupyterhub:
-  prePuller:
-    # hook prePuller shouldn't be enabled when configuring images in any other
-    # way than singleuser.image
-    hook:
-      enabled: true
   singleuser:
     memory:
       limit: 16G
@@ -16,9 +11,6 @@ jupyterhub:
         value: "climatematch"
         effect: "NoSchedule"
     defaultUrl: /lab
-    image:
-      name: wesleyban/climatematch-notebook
-      tag: v0.1
     # shared-public for collaboration
     # See https://github.com/2i2c-org/infrastructure/issues/2785
     storage: