archive-gh-me/gitpod
1
0
Fork 0
mirror of https://github.com/gitpod-io/gitpod.git synced 2025-12-08 17:36:30 +00:00
Code Issues Projects Releases Wiki Activity

[docs] Add upgrade guide

Browse Source
This commit is contained in:
Cornelius A. Ludmann 2021-02-04 09:12:35 +00:00 committed by Cornelius A. Ludmann
parent e42f7c8dec
commit c9dc572dd4
1 changed files with 27 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
docs/self-hosted/install/upgrade.md Normal file
View File

@ -0,0 +1,27 @@
---
url: /docs/self-hosted/latest/install/upgrade/
---
# Gitpod Self-Hosted Upgrade Notes
## Upgrading Gitpod from v0.6.0 to v0.7.0
With version 0.7.0 there are two major changes that require a user action. Both relate to the remote storage.
### Built-in MinIO is now accessable at minio.your-gitpod-domain.com
When you install Gitpod on your own Kubernetes installation, it brings a built-in MinIO object storage (unless disabled). As of v0.7.0, the built-in MinIO instance is accessable at https://minio.your-gitpod-domain.com. That's the reason that (for security reasons) we do not set a default access and secret key for the built-in MinIO installation anymore. That means, you need to add your own random keys in your values files like this:
```
minio:
accessKey: add-a-radom-access-key-here
secretKey: add-a-radom-secret-key-here
```
If you don't do this, `helm` will fail with the following message:
> minio access key is required, please add a value to your values.yaml
### Remote storage config has been moved to a new component
If you have a custom remote storage config (e.g. you use your own MinIO instance or the Google Cloud Storage), you need to move the config from the component `wsDaemon` to the new component `contentService`. See the [Storage Guide](../storage/) for an example.