diff --git a/config/clusters/2i2c/aup.values.yaml b/config/clusters/2i2c/aup.values.yaml index 8dd38478ca..beec96e623 100644 --- a/config/clusters/2i2c/aup.values.yaml +++ b/config/clusters/2i2c/aup.values.yaml @@ -65,8 +65,10 @@ jupyterhub: # allowed_users or admin_users, as such users are added to # JupyterHub's database on startup. # - # To properly revoke access, remove the user from the list, - # deploy the change, and finally delete the user via the + # To revoke admin status or access for a user when + # allow_existing_users is enabled, first remove the user from + # admin_users or allowed_users, then deploy the change, and + # finally revoke the admin status or delete the user via the # /hub/admin panel. # admin_users: diff --git a/config/clusters/2i2c/neurohackademy.values.yaml b/config/clusters/2i2c/neurohackademy.values.yaml index 1cc8148b85..97df782ea4 100644 --- a/config/clusters/2i2c/neurohackademy.values.yaml +++ b/config/clusters/2i2c/neurohackademy.values.yaml @@ -84,8 +84,10 @@ jupyterhub: # allowed_users or admin_users, as such users are added to # JupyterHub's database on startup. # - # To properly revoke access, remove the user from the list, - # deploy the change, and finally delete the user via the + # To revoke admin status or access for a user when + # allow_existing_users is enabled, first remove the user from + # admin_users or allowed_users, then deploy the change, and + # finally revoke the admin status or delete the user via the # /hub/admin panel. # admin_users: diff --git a/config/clusters/carbonplan/common.values.yaml b/config/clusters/carbonplan/common.values.yaml index a8b907ddcd..cb99bac399 100644 --- a/config/clusters/carbonplan/common.values.yaml +++ b/config/clusters/carbonplan/common.values.yaml @@ -215,8 +215,10 @@ basehub: # allowed_users or admin_users, as such users are added to # JupyterHub's database on startup. # - # To properly revoke access, remove the user from the list, - # deploy the change, and finally delete the user via the + # To revoke admin status or access for a user when + # allow_existing_users is enabled, first remove the user from + # admin_users or allowed_users, then deploy the change, and + # finally revoke the admin status or delete the user via the # /hub/admin panel. # admin_users: diff --git a/config/clusters/cloudbank/howard.values.yaml b/config/clusters/cloudbank/howard.values.yaml index 9dbd30268a..5e77e99332 100644 --- a/config/clusters/cloudbank/howard.values.yaml +++ b/config/clusters/cloudbank/howard.values.yaml @@ -59,8 +59,10 @@ jupyterhub: # allowed_users or admin_users, as such users are added to # JupyterHub's database on startup. # - # To properly revoke access, remove the user from the list, - # deploy the change, and finally delete the user via the + # To revoke admin status or access for a user when + # allow_existing_users is enabled, first remove the user from + # admin_users or allowed_users, then deploy the change, and + # finally revoke the admin status or delete the user via the # /hub/admin panel. # admin_users: diff --git a/config/clusters/cloudbank/lacc.values.yaml b/config/clusters/cloudbank/lacc.values.yaml index a04dba1087..8c6c41b29a 100644 --- a/config/clusters/cloudbank/lacc.values.yaml +++ b/config/clusters/cloudbank/lacc.values.yaml @@ -59,8 +59,10 @@ jupyterhub: # allowed_users or admin_users, as such users are added to # JupyterHub's database on startup. # - # To properly revoke access, remove the user from the list, - # deploy the change, and finally delete the user via the + # To revoke admin status or access for a user when + # allow_existing_users is enabled, first remove the user from + # admin_users or allowed_users, then deploy the change, and + # finally revoke the admin status or delete the user via the # /hub/admin panel. # admin_users: diff --git a/config/clusters/cloudbank/palomar.values.yaml b/config/clusters/cloudbank/palomar.values.yaml index a95b5a6430..91dcb3349c 100644 --- a/config/clusters/cloudbank/palomar.values.yaml +++ b/config/clusters/cloudbank/palomar.values.yaml @@ -59,8 +59,10 @@ jupyterhub: # allowed_users or admin_users, as such users are added to # JupyterHub's database on startup. # - # To properly revoke access, remove the user from the list, - # deploy the change, and finally delete the user via the + # To revoke admin status or access for a user when + # allow_existing_users is enabled, first remove the user from + # admin_users or allowed_users, then deploy the change, and + # finally revoke the admin status or delete the user via the # /hub/admin panel. # admin_users: diff --git a/config/clusters/cloudbank/sbcc-dev.values.yaml b/config/clusters/cloudbank/sbcc-dev.values.yaml index 6aee2fa79e..98e01568a0 100644 --- a/config/clusters/cloudbank/sbcc-dev.values.yaml +++ b/config/clusters/cloudbank/sbcc-dev.values.yaml @@ -62,8 +62,10 @@ jupyterhub: # allowed_users or admin_users, as such users are added to # JupyterHub's database on startup. # - # To properly revoke access, remove the user from the list, - # deploy the change, and finally delete the user via the + # To revoke admin status or access for a user when + # allow_existing_users is enabled, first remove the user from + # admin_users or allowed_users, then deploy the change, and + # finally revoke the admin status or delete the user via the # /hub/admin panel. # admin_users: diff --git a/config/clusters/cloudbank/sbcc.values.yaml b/config/clusters/cloudbank/sbcc.values.yaml index e5557cf6ac..2fc8495102 100644 --- a/config/clusters/cloudbank/sbcc.values.yaml +++ b/config/clusters/cloudbank/sbcc.values.yaml @@ -62,8 +62,10 @@ jupyterhub: # allowed_users or admin_users, as such users are added to # JupyterHub's database on startup. # - # To properly revoke access, remove the user from the list, - # deploy the change, and finally delete the user via the + # To revoke admin status or access for a user when + # allow_existing_users is enabled, first remove the user from + # admin_users or allowed_users, then deploy the change, and + # finally revoke the admin status or delete the user via the # /hub/admin panel. # admin_users: diff --git a/config/clusters/cloudbank/staging.values.yaml b/config/clusters/cloudbank/staging.values.yaml index 31f42cccc3..b45e22d8ae 100644 --- a/config/clusters/cloudbank/staging.values.yaml +++ b/config/clusters/cloudbank/staging.values.yaml @@ -59,8 +59,10 @@ jupyterhub: # allowed_users or admin_users, as such users are added to # JupyterHub's database on startup. # - # To properly revoke access, remove the user from the list, - # deploy the change, and finally delete the user via the + # To revoke admin status or access for a user when + # allow_existing_users is enabled, first remove the user from + # admin_users or allowed_users, then deploy the change, and + # finally revoke the admin status or delete the user via the # /hub/admin panel. # admin_users: diff --git a/config/clusters/cloudbank/tuskegee.values.yaml b/config/clusters/cloudbank/tuskegee.values.yaml index 9c0c746201..40d56e897c 100644 --- a/config/clusters/cloudbank/tuskegee.values.yaml +++ b/config/clusters/cloudbank/tuskegee.values.yaml @@ -59,8 +59,10 @@ jupyterhub: # allowed_users or admin_users, as such users are added to # JupyterHub's database on startup. # - # To properly revoke access, remove the user from the list, - # deploy the change, and finally delete the user via the + # To revoke admin status or access for a user when + # allow_existing_users is enabled, first remove the user from + # admin_users or allowed_users, then deploy the change, and + # finally revoke the admin status or delete the user via the # /hub/admin panel. # admin_users: diff --git a/config/clusters/gridsst/common.values.yaml b/config/clusters/gridsst/common.values.yaml index a858234963..b2bffbfd94 100644 --- a/config/clusters/gridsst/common.values.yaml +++ b/config/clusters/gridsst/common.values.yaml @@ -61,8 +61,10 @@ basehub: # allowed_users or admin_users, as such users are added to # JupyterHub's database on startup. # - # To properly revoke access, remove the user from the list, - # deploy the change, and finally delete the user via the + # To revoke admin status or access for a user when + # allow_existing_users is enabled, first remove the user from + # admin_users or allowed_users, then deploy the change, and + # finally revoke the admin status or delete the user via the # /hub/admin panel. # admin_users: diff --git a/config/clusters/jupyter-meets-the-earth/common.values.yaml b/config/clusters/jupyter-meets-the-earth/common.values.yaml index 0776b2801d..dd9f7364e5 100644 --- a/config/clusters/jupyter-meets-the-earth/common.values.yaml +++ b/config/clusters/jupyter-meets-the-earth/common.values.yaml @@ -247,8 +247,10 @@ basehub: # allowed_users or admin_users, as such users are added to # JupyterHub's database on startup. # - # To properly revoke access, remove the user from the list, - # deploy the change, and finally delete the user via the + # To revoke admin status or access for a user when + # allow_existing_users is enabled, first remove the user from + # admin_users or allowed_users, then deploy the change, and + # finally revoke the admin status or delete the user via the # /hub/admin panel. # admin_users: diff --git a/config/clusters/meom-ige/common.values.yaml b/config/clusters/meom-ige/common.values.yaml index 1b2adedaab..13145dfb45 100644 --- a/config/clusters/meom-ige/common.values.yaml +++ b/config/clusters/meom-ige/common.values.yaml @@ -113,8 +113,10 @@ basehub: # allowed_users or admin_users, as such users are added to # JupyterHub's database on startup. # - # To properly revoke access, remove the user from the list, - # deploy the change, and finally delete the user via the + # To revoke admin status or access for a user when + # allow_existing_users is enabled, first remove the user from + # admin_users or allowed_users, then deploy the change, and + # finally revoke the admin status or delete the user via the # /hub/admin panel. # admin_users: diff --git a/config/clusters/openscapes/common.values.yaml b/config/clusters/openscapes/common.values.yaml index 2f9a057b7c..429becc556 100644 --- a/config/clusters/openscapes/common.values.yaml +++ b/config/clusters/openscapes/common.values.yaml @@ -81,8 +81,10 @@ basehub: # allowed_users or admin_users, as such users are added to # JupyterHub's database on startup. # - # To properly revoke access, remove the user from the list, - # deploy the change, and finally delete the user via the + # To revoke admin status or access for a user when + # allow_existing_users is enabled, first remove the user from + # admin_users or allowed_users, then deploy the change, and + # finally revoke the admin status or delete the user via the # /hub/admin panel. # admin_users: diff --git a/config/clusters/pangeo-hubs/coessing.values.yaml b/config/clusters/pangeo-hubs/coessing.values.yaml index d53450e095..0235e3e56c 100644 --- a/config/clusters/pangeo-hubs/coessing.values.yaml +++ b/config/clusters/pangeo-hubs/coessing.values.yaml @@ -65,8 +65,10 @@ basehub: # allowed_users or admin_users, as such users are added to # JupyterHub's database on startup. # - # To properly revoke access, remove the user from the list, - # deploy the change, and finally delete the user via the + # To revoke admin status or access for a user when + # allow_existing_users is enabled, first remove the user from + # admin_users or allowed_users, then deploy the change, and + # finally revoke the admin status or delete the user via the # /hub/admin panel. # admin_users: