-
Notifications
You must be signed in to change notification settings - Fork 389
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.
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
Change component name from dind to image-builder #1543
Conversation
In parallel of the work from jupyterhub#1531, this change will allow the use of other builders than Docker without being tied to its nomenclature which might make the whole a bit confusing when deploying and debugging.
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.
This change makes sense to me.
@minrk @consideRatio Are you aware of anything that relies on component: dind
?
I'm not sure, about tooling relying on identifying the pods by the I looked but found nothing. Seems reasonable to me! I wonder if upgrading to this binderhub version will make the active build pods be abandoned or similar? If so its good that such notes are part of the PR description so that upgrades can be made during low load at least. |
Yeah, if anything I would guess it's only something in grafana or possibly a network policy. |
Thanks all, merging! |
`component=dind` is changing to `component=image-builder` jupyterhub/binderhub#1543
jupyterhub/binderhub#1543 Merge pull request #1543 from sgaist/refactor_dind_label
In parallel of the work from #1531, this change will allow the use of other builders than Docker without being tied to its nomenclature which might make the whole a bit confusing when deploying and debugging.
Part of #1513