From bbdc8d0085e028fc7506194949ac0b52a8d3e32d Mon Sep 17 00:00:00 2001 From: YuviPanda Date: Wed, 5 Jul 2023 17:55:58 -0700 Subject: [PATCH] Add note about initial node-pool size for workshops Document https://github.com/2i2c-org/infrastructure/pull/2758#issuecomment-1622756467 --- docs/howto/features/dedicated-nodepool.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/docs/howto/features/dedicated-nodepool.md b/docs/howto/features/dedicated-nodepool.md index a9273eb5b7..c880e09841 100644 --- a/docs/howto/features/dedicated-nodepool.md +++ b/docs/howto/features/dedicated-nodepool.md @@ -69,4 +69,13 @@ Some hubs on shared clusters require dedicated nodepools, for a few reasons: ``` This tells JupyterHub to place user pods from this hub on the nodepool we had - just created! \ No newline at end of file + just created! + +## Node type and minimum nodepool size considerations + +When setting up a dedicated node pool for a hub, particularly a hub supporting +an *event*, it's important to consider the node type and minimum node size +used. As there will likely only be minimal number of users until the event +starts, it's helpful to set the *minimum node pool size* to 0 until at least +*a week* before the start of the event. A smaller node type is also adviced +until a week before the event.