d66c18e726
- restrict to _one_ ingress mode: `hosts` with subdomain certs - remove all references to the old self-hosted repository - replace all automatisms with copy-n-paste - try to reduce text :-)
2.1 KiB
| url |
|---|
| /docs/self-hosted/latest/install/install-on-kubernetes/ |
Install Gitpod Self-Hosted on Kubernetes
This section describes how to install Gitpod on any Kubernetes cluster. Gitpod also provides more optimized installations offering better performance for particular cloud providers:
- Google Cloud Platform: Install Gitpod in a blank GCP project using a script that automates the procedure.
- AWS: Install Gitpod on AWS using a script that automates the procedure.
Gitpod is installed using Helm. The chart can be found here.
Installation
To initiate the deployment run the following commands:
git clone https://github.com/gitpod-io/gitpod
cd gitpod/chart
helm repo add charts.gitpod.io https://charts.gitpod.io
helm repo add stable https://charts.helm.sh/stable
helm repo add stable https://helm.min.io/
helm repo update
helm dep up
helm install gitpod .
Review the deployment worked properly by running
kubectl get pods. Eventually all pods should be up-and-running. In case they are not have a look the the Troubleshooting Guide
-
Configure ingress into the cluster
-
Go to https://<your-domain.com> and follow the steps to complete the installation.
Recommended Configuration
Without further configuration the Helm chart installs a working Gitpod installation in a lot of scenarios. Yet, there are certain things you might want to review when installing Gitpod for long term use and/or a bigger audience:
- Database: Configure where Gitpod stores all internal runtime data.
- Storage: Configure where Gitpod persists workspace content.
- Docker Registry: Configure where Gitpod stores workspace images that are build at runtime.
Customization
Further customizations:
- Kubernetes Nodes: Configure file system layout and the workspace's node associativity.
- Workspaces: Configure workspace sizing.