-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[self-hosted] Support newer releases of Ubuntu and Kubernetes #4053
Comments
I feel the problem is that there is a lot of low level access you get (root / Docker usage) which entails a lot of fiddling with the nodes. That trigger issues when you stray from the gitpod devs' set up (Ubuntu 18.04, Kubernetes support is fine). |
👋 @cyrilcros and @flickerfly. There's some mighty fine suggestions right there and some of them have been incorporated into the recent v0.10.0 release. Let's keep this issue open until more of your suggestions are implemented. If you would like to help out with contribution then 🧡 let me know how I can help. ICYMI some of the improvements shipped over the last two weeks:
|
Requirements were documented last night at https://www.gitpod.io/docs/self-hosted/latest/requirements |
ps: @cyrilcros and @flickerfly - come join www.gitpod.io/chat in the #gitpod-self-hosted room. |
I have 0.10.0 running on Ubuntu 20.04 with RKE 1.20.11 using containerd 1.4.9. Took some work figuring out the Helm answers but it appears to be fairly stable. What info do you need to verify RKE 1.20.11 as a supported platform? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@ghuntley Would you mind updating the https://www.gitpod.io/docs/self-hosted/latest/requirements page to at least mention Gitpod now works on RKE with the recommended workaround posted in the referenced Github issue comments? We've had Gitpod 0.10.0 running now for 3+ months in production on RKE 1.20.x without issue. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Current state
Basically, self-hosted currently requires Ubuntu 18.04 and Kubernetes ~1.17 - 1.18 (EDIT: well, I am unfair here for Kubernetes). It would be very desirable to move the current support matrix closer to the Ubuntu and Kubernetes respective release cycles.
For instance, as pointed in #3969, Ubuntu 18.04 is now 3 years old, and 20.04 has been around for a year. This issue is by the way the same request, but for workspace image support whereas I am talking self-hosted...
It means:
Improvement suggestions for self-hosted
I fully understand this is a massive amount of work and not realistic to always stay on top of this. However, could you please:
values.yaml
you used - without secrets)broken in Ubuntu 20.04
, to keep track of what is missing, and possibly allow people to help. That could be a pinned issue.ws-daemon
,blobserve
, why is there aregistry-facade
, why is there aws-manager
plus aws-manager-bridge
, which of them have access to thekubeapi-server
or are open to the Internet. That would help with error reporting.This being said, many thanks for offering this software as a self-hosted option, I definitely prefer it to Eclipse Che and others..... It has a lot of potential, it could do for programming what the Jupyterhub project does for Jupyter notebooks.
The text was updated successfully, but these errors were encountered: