-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Collaborate on prototype of in-workspace image build #15611
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
Comments
@loujaybee do y'all have any target dates for which you'd like to have a prototype working by (not in main, of course)? I ask to help set expectations and timebox this activity. Let us know? 🙏 cc: @iQQBot @utam0k @laushinka |
@utam0k does IDE team need anything else from you? If yes, can you share a summary of what is needed and update the issue description? You may need to talk synchronously with @iQQBot, to better understand remaining challenges/concerns. To review, none of the workspacekit experimental branches from IDE team are planned to merge to main. If IDE team does intend to merge any of the experimental workspacekit branches to main, please review thoroughly with both @Furisto and @csweichel . 🙏 cc: @jenting @WVerlaek , should you see a workspacekit PR enter our queue for review, please defer to ☝️ |
I have updated the description |
Thanks for the 🏆 diagram, @utam0k ! 🤝 |
Hi @laushinka, is there a time box for this activity? I ask because it's been running for a couple weeks, and appears to be starting to hit limits. Hi @utam0k , @akosyakov bumped into some trouble here, wdyt? Are there any opportunities to help improve performance? 🤔 |
@kylos101 I'll check it 👀 |
Hi, @kylos101! Sorry for the lack of updates in this issue.
How does that sound to you and @utam0k? 🙏🏽 |
@laushinka Thanks for giving me your specific plan. Make sense a lot. But we are having trouble implementing the prototype. I think we need to continue to collaborate closely. |
Really appreciate your help, @utam0k 🧡 There is no pressure from our side, and as long as it doesn't interfere with your other priorities. |
Thanks @laushinka ! That sounds great Re: closing this issue to focus on other priorities. As a heads up, if a PR review and subsequent approval are desired in the future, we'll need to be careful and loop in others (Chris), too. @utam0k is there anything you'd like to record or save, as part of this collaboration, before closing this issue? Closing this issue will help us focus on other priorities for Workspace Team. |
FYI, I closed #15766 |
I don't have anything more for now. @laushinka If your team needs help again, feel free to ask our team! Let's make it together! |
Is your feature request related to a problem? Please describe
IDE team is working #7671, and has started a related prototype to do in-workspace image builds in https://github.com/gitpod-io/gitpod/tree/pd/workspacekit, the proposed design is outlined here. The intent behind https://github.com/gitpod-io/gitpod/tree/pd/workspacekit is not to create a branch that gets merged back to main. However, that could change? It depends how "good" the experience is.
Describe what you'd like
@utam0k , when you return from vacation, can you talk with @iQQBot? He might need help from Workspace Team, he might not. 😄
Are they happy with the new experience for building images in-workspace? Would they like you to review any of the code in the branch, to help improve the experience for the branch?
Run two supervisors in a workspace pod at the same time
We need to create two IP addresses on ring1 for each of supervisor so as to go for this design
This can be done by editing the nsinsider function we have been using.
gitpod/components/ws-daemon/nsinsider/main.go
Lines 264 to 427 in 0c84d03
go to ASCIIFlow link)
or I have an idea to use eBPF but it is not simple.
Additional context
Thoughts about potential risks if we run the image builder CLI in-workspace:
docker run
@loujaybee @laushinka @akosyakov How does IDE team plan to collect feedback on the prototype? @akosyakov shared that the experience is currently poor / not doable in preview environments. Also, I am creating this issue because our team is highly distributed, therefore, we must default to async communication to share context.
@atduarte 👋
The text was updated successfully, but these errors were encountered: