Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add note about initial node-pool size for workshops #2765

Merged
merged 2 commits into from
Jul 6, 2023
+10 −1
Merged

Add note about initial node-pool size for workshops #2765

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bbdc8d0
Add note about initial node-pool size for workshops
yuvipanda Jul 6, 2023
4d012f5
Fix typo
yuvipanda Jul 6, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion docs/howto/features/dedicated-nodepool.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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!
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 advised
until a week before the event.