Request createWorkspace failed with message: 14 UNAVAILABLE

Hi everyone! I install gitpod on premise and once I try to open a github repo I get the following error: "Request createWorkspace failed with message: 14 UNAVAILABLE".

This is the log of the call:

{"upstreamAddr":"10.43.126.88:3000","requestScheme":"https","requestHost":"kerberus-gitpod.ddns.net","requestTime":"40.006","remotePort":"6033","serverName":"kerberus-gitpod.ddns.net","httpRequest":{"requestSize":"776","responseSize":"408","userAgent":"Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Mobile Safari/537.36","remoteIp":"10.42.3.0","serverIp":"10.42.1.12","latency":"40.006","protocol":"HTTP/1.1","requestMethod":"GET","status":"101","requestUrl":"/api/gitpod"},"connection":"2235","httpConnection":"Upgrade","cookies":{"*kerberus_gitpod_ddns_net*":"s%3Adf177a24-48ac-41d1-a0b6-ab9a7c222ac8.UGFFnw2CnLs6Niarm%2BsqVoU%2F2h4Y%2BHeTRRJVYMOPXq0","gitpod-user":"loggedIn","user-platform":"6c7f835a-6560-44e1-99d4-973ed6fbdb06"},"httpUpgrade":"websocket","proxyHost":"ws-apiserver","serverPort":"443","proxyPort":"80","severity":200,"requestHeaders":{"pragma":"no-cache","origin":"https://kerberus-gitpod.ddns.net","sec-websocket-version":"13","host":"kerberus-gitpod.ddns.net","cache-control":"no-cache","accept-language":"it-IT,it;q=0.9,en-US;q=0.8,en;q=0.7,es;q=0.6","user-agent":"Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Mobile Safari/537.36","sec-websocket-extensions":"permessage-deflate; client_max_window_bits","sec-websocket-key":"Cw8b4OhPqB43Iy3RdKmkBw==","accept-encoding":"gzip, deflate, br","connection":"Upgrade","upgrade":"websocket"},"responseHeaders":{"upgrade":"websocket","access-control-allow-origin":"https://kerberus-gitpod.ddns.net","sec-websocket-extensions":"permessage-deflate","access-control-expose-headers":"Authorization","sec-websocket-accept":"Ssra3rclUOaDK0KWtPzOfzOazRk=","access-control-allow-credentials":"true","connection":"upgrade","x-gitpod-region":"production.gitpod.local.00"},"context":{"sessionId":"df177a24-48ac-41d1-a0b6-ab9a7c222ac8"}}

For additional information:

  • Which version of Gitpod have you installed? I installed gitpod with the helm chart and I didn’t specify the version, so I guess it’s pointing to the 0.8.0 version.
  • On which Kubernetes provider have you installed Gitpod (GCP, k3s, AWS, …)? RKE from Rancher Labs
  • Which networking do you use (e.g. Calico)? Flannel
  • How does your values.yaml look like? It is really simple:

hostname: kerberus-gitpod.ddns.net

minio:
accessKey: gitpod-random-access-key
secretKey: gitpod-random-secret-key

Could you please help me to find out the issue?

Thanks,

Diego

A similar issue is described here: Request createWorkspace failed with message: 14 UNAVAILABLE · Issue #2004 · gitpod-io/gitpod · GitHub

Hi @braghettos,

Please note that we currently support GKE and k3s only.

What you could try is to use Calico. As far as I remember, we saw some problems with other network providers.

Cornelius

Hi @corneliusludmann ,

could I help somehow in supporting RKE as a Kubernetes distribution?

Of course, you can fix issues that you experience with RKE. Pull requests to our repo are very welcome.

The reason that we limit the supported Kubernetes distributions that we officially support is that we get too many support requests to different distributions and we cannot test them all regularly. In contrast to other products that run as Kubernetes applications, Gitpod heavily makes use of some Kubernetes internals to run workspaces. That makes it harder to support all kinds of Kubernetes distributions out there.

A good start for you would be to install Calico instead of Flannel (when this is possible on RKE). You could also search this community formum. As far as I know, other users have tried Gitpod on RKE already.

I think it would be a god idea to put info about your Platform Support Matrix right at the top of the self-hosted installation guide. I expect many people will spend ages (like I have as well :wink: ) with other solutions before also trying k3s.

There is a good amount of information missing in the docs (like using Calico instead of Flannel, recommended setup and settings for k3s as this is key support Kubernetes flavour) for a good setup experience with steps to follow to save people time with trouble shooting their way through getting things to work. Once I get the setup I am testing working (k3s on Hetzner, launched with terraform and managed in Rancher) I am happy to share what I have found to facilitate this.

1 Like

Trying to install 0.9.0-alpha1 on the latest k3s release.

Apart from a bunch of warnings like this, it seems to install ok:
rbac.authorization.k8s.io/v1beta1 ClusterRole is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v1 ClusterRol

But - trying to create a new workspace from Gitlab.com I get the error referenced in this thread.