Skip to content

Commit 8c7e877

Browse files
committed
Reduce example complexity
1 parent 1a3ddda commit 8c7e877

File tree

1 file changed

+7
-16
lines changed

1 file changed

+7
-16
lines changed

jupyterhub/values.schema.yaml

Lines changed: 7 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -233,6 +233,8 @@ properties:
233233
```python
234234
c.JupyterHub.admin_access = true
235235
c.JupyterHub.admin_users = ["jovyan1", "jovyan2"]
236+
c.KubeSpawner.k8s_api_request_timeout = 10
237+
c.GitHubOAuthenticator.allowed_organizations = ["jupyterhub"]
236238
```
237239
238240
Then, you would be able to represent it with this configuration like:
@@ -245,22 +247,11 @@ properties:
245247
admin_users:
246248
- jovyan1
247249
- jovyan2
248-
```
249-
250-
__Example__
251-
252-
If your kubernetes pods take longer than usual to spawn, the users notebooks
253-
may fail to spawn with an error like `<user>'s server failed to start in 30000
254-
seconds, giving up`. In such scenarios, you may need to adjust
255-
[KubeSpawner defaults](https://jupyterhub-kubespawner.readthedocs.io/en/latest/spawner.html#kubespawner.KubeSpawner.k8s_api_request_timeout)
256-
which can also be done using `hub.config`. For example,
257-
258-
```yaml
259-
hub:
260-
config:
261-
KubeSpawner:
262-
k8s_api_request_timeout: 3600
263-
...
250+
KubeSpawner:
251+
k8s_api_request_timeout: 10
252+
GitHubOAuthenticator:
253+
allowed_organizations:
254+
- jupyterhub
264255
```
265256
266257
```{admonition} YAML limitations

0 commit comments

Comments
 (0)