Add new blog post about dask-gateway new feature #614
+32
−0
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,32 @@ | ||||||
| --- | ||||||
| title: "Allow limiting access to Dask Gateway based on group membership" | ||||||
| slug: "dask-gateway-membership-access" | ||||||
| date: 2026-06-10 | ||||||
| authors: | ||||||
| - Georgiana Dolocan | ||||||
| categories: | ||||||
| tags: | ||||||
| - open-source | ||||||
| - community | ||||||
| categories: | ||||||
| - community-impact | ||||||
| - upstream-impact | ||||||
| --- | ||||||
|
|
||||||
| Starting with [Dask Gateway](https://gateway.dask.org/) version [v2026.3.0](https://gateway.dask.org/changelog.html#v2026-3-0), JupyterHub access scopes support has been added to Dask-Gateway. | ||||||
|
|
||||||
| What this means for JupyterHub users, is that hub admins can control, via JupyterHub RBAC, which hub users or groups have access to Dask-Gateway. This is especially important from the cost perspective, as it allows admins to control who can access Dask-Gateway and thus have more control over their cloud spend. | ||||||
|
|
||||||
| 2i2c is deploying this version alongside the hubs, so all communities we serve that are using Dask-Gateway, now have access to this feature. | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||
|
|
||||||
| Checkout | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||
| - the [Control access to Dask Gateway](https://docs.2i2c.org/admin/user-management/dask-access/) page for how to ask 2i2c to set up this feature for your hub | ||||||
| - the [Dask Gateway documentation](https://gateway.dask.org/authentication.html#using-jupyterhub-s-authentication) for more details on how it works. | ||||||
|
|
||||||
| ## Acknowledgements | ||||||
|
|
||||||
| - To [EarthScope](/collaborators/earthscope/) for motivating this work and providing feedback | ||||||
| - To [MinRK](https://github.com/minrk) for adding this feature to Dask-Gateway | ||||||
| - To [Yuvi](../../../authors/yuvi-panda/) for code review and guidance on the implementation | ||||||
| - To [Erik](../../../authors/erik-sundell/) for code review | ||||||
| - To our [member communities](../../../members/) for supporting us and giving us the capacity to invest in upstream open source engagement | ||||||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.