Gitpod Is Now Open Source. Learn More.
- Configure Your Project
- Docker Configuration
- Start Tasks
- VS Code Extensions
- Exposing Ports
- Prebuilt Workspaces
- Environment Variables
- Workspace Location
- Editor Configuration
- Gitpod Self-Hosted
- Install on Google Cloud Platform
- Install on Amazon Web Services
- Install on self-managed Kubernetes
- Configure OAuth
- Configure a Domain
- Configure HTTPS Certificates
- Configure a Database
- Configure a Docker Registry
- Configure Storage
- Configure Nodes
- Configure Workspaces
- Languages & Frameworks
Configure the nodes (computers or virtual machines) that Kuberntes runs Gitpod’s workspace pods on.
Gitpod schedules two kinds of workloads: the Gitpod installation itself (which we refer to as meta) and the workspaces. Ideally both types of workloads run on seperate nodes to make makes scaling easier. Depending on your cluster size that may not be feasible though. Either way, you need two node labels in your cluster:
gitpod.io/workload_meta=truewhich marks the “meta” nodes and
gitpod.io/workload_workspace=truewhich marks the workspace nodes.
If you want to “mix ‘n match”, i.e., don’t separate the nodes, you can simply run:
kubectl label node --all gitpod.io/workload_meta=true gitpod.io/workload_workspace=true
Gitpod relies on the node’s filesystem for making workspace content available, as well as for storing Theia. By default workspace data is placed in
/data and Theia is copied to
/theia. Depending on your node setup the root filesystem maybe read-only or slow.
We recommend you change those two paths so that they’re located on an SSD or some other form of fast local storage.
To do this:
echo values/node-layout.yaml >> configuration.txt
values/node-layout.yamlchange the values to match your installation
Still Have Questions?
Please reach out. We’re happy to answer them.