June 29, 2022

June Self-Hosted Release

We’ve released a new version of Self-Hosted Gitpod. Update instructions can be found in our update guide. You can read more about how to install it from scratch in our documentation. More details on this release can be found in GitHub.

Note: If you are on a paid Self-Hosted plan, this release will be promoted to your release channel in one week.

For feedback, please raise an issue or chat with us.

New way to try out Gitpod: Local Preview (alpha)

You can now try out Gitpod Self-Hosted without having to spin up a Kubernetes cluster - via a simple docker run command. This will spin up Gitpod locally on your machine and enable you to experience what developing on Gitpod is like. Note that currently, only Linux-based systems are supported (Windows and Mac(Intel) are being worked on) and that unfortunately prebuilds will not work. You can read up on how to get going in the Local Preview Guide. Local preview is still in alpha, so we would appreciate any feedback you may have!

More flexibility regarding registries for airgapped environments

If you are using Gitpod in an airgapped environment you can now specify the container registry you want to use to store workspace images that Gitpod builds for you. By default, it will use an in-cluster registry. Previously, it would always use the same registry that is used during installation to download the images related to Gitpod.

Fixes and improvements

• We have added a customer_id field to the telemetry that is sent from a self-hosted instance. This helps us map an installation to a customer for support purposes. Note that this field is not being populated for users using the community plan and is only relevant to those on a professional plan.

A full list of changes can be found in the release notes on GitHub.