Skip to content

Add new blog post about dask-gateway new feature#614

Open
GeorgianaElena wants to merge 1 commit into
2i2c-org:mainfrom
GeorgianaElena:blog-post
Open

Add new blog post about dask-gateway new feature#614
GeorgianaElena wants to merge 1 commit into
2i2c-org:mainfrom
GeorgianaElena:blog-post

Conversation

@GeorgianaElena

Copy link
Copy Markdown
Member

Fixes #613

@netlify

netlify Bot commented Jun 10, 2026

Copy link
Copy Markdown

Deploy Preview for 2i2c-org ready!

Name Link
🔨 Latest commit f9acd29
🔍 Latest deploy log https://app.netlify.com/projects/2i2c-org/deploys/6a2952053665290008d41fb6
😎 Deploy Preview https://deploy-preview-614--2i2c-org.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@aprilmj aprilmj left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this post! <3


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.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.
That means hub admins can now set, via JupyterHub role-based access control (RBAC), which hub users or groups have access to Dask-Gateway. This is especially important from a cost perspective, as it allows admins to control who can access Dask-Gateway and thus have more control over their cloud spend.


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.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
2i2c is deploying this version alongside the hubs, so all communities we serve that are using Dask-Gateway, now have access to this feature.
If your community is part of the 2i2c member network, you can take advantage of this feature now. 2i2c is deploying the new Dask-Gateway version alongside our hubs, so all communities we serve that are using Dask-Gateway now have access to this feature.


2i2c is deploying this version alongside the hubs, so all communities we serve that are using Dask-Gateway, now have access to this feature.

Checkout

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Checkout
Want to know more, or set this up on your hub? Check out:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Blog about the group membership dask-gateway version

2 participants