This page informs you if there are specific considerations to take into account when upgrading to a specific version. If no breaking changes and thus specific recommendations when updating are mentioned here, please follow the normal upgrade procedure mentioned on the Updating your Gitpod Installation page.
You can now configure the service type of the proxy service in the installation UI (see image below) - you do not need to upload a
.yaml file as a config patch anymore to configure this. However, having it in the config patch will still work until December.
If you are setting a resource limit for workspaces via a config-patch, the way to set these limits has changed slightly:
workspace: resources: requests: cpu: "3" memory: 15Gi limits: cpu: "4" memory: 21Gi
You can now have two types of limits you can set:
- A min limit: this is always respected
- A burst limit: this is allowed for short periods, e.g. to allow for high-intensity workloads during workspace startup
workspace: resources: requests: cpu: "3" memory: 15Gi limits: cpu: min: "2" burst: "6" memory: 21Gi
We’ve moved the configuration of the default workspace image and the default base image registry whitelist out of the experimental section of the config-patch file. The latter was also renamed. Using them in the experimental section will still work for the time being (until approx. December 2022).
experimental: webApp: server: defaultBaseImageRegistryWhitelist: - <allowed registries> workspaceDefaults: workspaceImage: <path to your default workspace image>
workspace: workspaceImage: <path to your default workspace image> containerRegistry: privateBaseImageAllowList: - <allowed registries>