December 24, 2021
Self-managed k3s on GCP
Gitpod’s services run on Kubernetes and are what you would consider a “classic cloud-native application”. When you start a workspace for your project, we also run that on Kubernetes, but the requirements are very different from what Gitpod services need.
To run your workspaces, we deeply integrate with the Kernel, the container runtime and the Kubernetes control plane.
Up until recently, everything above ran on Google Cloud’s Kubernetes Engine (GKE). This continues to be the case for Gitpod’s services, but we moved user workspaces to self-managed k3s on GCP.
In short, this move brings better performance that will benefit your daily work, but also gets us closer to upstream and provides us with more flexibility. It is a foundation we put in place to build upon in the weeks and months to come!
Before you decide to follow our lead though, please see our CTO Chris’ in-depth explanation of benefits, gotchas and overall details of this migration.
- #7312 - Profile of the user who already added a project is linked.
- #7177 - Allow auth provider secrets to be passed in via a secret
- #7012 - Allow setting a name and a description for each port on .gitpod.yml
- #7354 - Fix Team Workspace Success Criteria dashboard
- #7107 - [installer]: update docker-registry to allow for pod security policy application
- #6827 - 1. [installer] Add a namespace for the cert-manager self-signing issuer so it can be uninstalled using the configmap.2. [installer] Set EnableLocalApp to true by default.
- #7206 - [installer]: correct the starts_with validation on the config
- #7200 - [installer]: separate server and IDE components
- #7163 - Improved start page when a GitHub app is not installed.