Space On-Premises Installation
As an alternative to using Space as a service, you can get your own self-managed Space instance (or Space on-premises). It implies that you install, manage, and maintain Space on your own.
Limitations of Space on-premises EAP
Currently, Space on-premises is in the Early Access Preview (EAP) state and is available only to a limited number of users on request. The EAP version has the following limitations:
The EAP license is valid only till July 1, 2021.
The max number of users is 500.
The max number of parallel Automation (CI/CD) jobs is 10.
Space on-premises runs in a Kubernetes cluster. The cluster itself can run in the following environments:
There are two ways to install Space on-premises:
- (Recommended) Using the deployment script
The deployment script guides you through the installation process letting you specify the most important settings. The result of its work is a values YAML file that configures a cluster with Space on-premises.
- Using a Helm chart
jetbrains-spaceHelm chart that contains all the required dependencies. We recommend this installation method only for complex clusters that cannot be configured with the deployment script. To perform this installation:
Get the chart from the repository:
Prepare a values YAML file with Space on-premises configuration. As a basis, you can use either the following template or a values file generated by the deployment script.
Install Space on-premises using the chart.
We recommend that you start with a proof-of-concept installation on your local machine. It will let you get acquainted with Space on-premises configuration and better understand the requirements for your future production installation.