[self-hosted] Prepare release of 0.7.0 (gitpod-io#3099)

* [docs] Make Self-hosted version explicit (0.7.0)

* [chart] bump version: 0.7.0-beta1

* [docs] Update for 0.7.0

* [docs] More troubleshooting from 0.6.0->0.7.0 upgrade experience

* [docs] Add 'Upgrade' section

* [chart] bump version to 0.7.0

Author: geropl

chart/values.yaml

@@ -1,7 +1,7 @@
 # Copyright (c) 2020 Gitpod GmbH. All rights reserved.
 # Licensed under the MIT License. See License-MIT.txt in the project root for license information.
 
-version: 0.6.0-beta5
+version: "0.7.0"
 
 hostname: localhost
 # ingressModes determines how Gitpod makes workspaces and their ports available. Possible values are:

docs/self-hosted/install/configure-ingress.md

@@ -55,12 +55,12 @@ To configure the HTTPS certificates for your domain
     ```bash
     kubectl create secret generic https-certificates --from-file=secrets/https-certificates
     ```
- 4. Afterwards, do an `helm upgrade --install -f values.custom.yaml gitpod gitpod.io/gitpod` to apply the changes.
+ 4. Afterwards, do an `helm upgrade --install -f values.custom.yaml gitpod gitpod.io/gitpod --version=0.7.0` to apply the changes.
  
 
 ### Using Let's Encrypt to generate HTTPS certificates
 
-The most accessible means of obtaining HTTPS certificates is using [Let's Encrypt](https://letsencrypt.org/). It provides free certificats to anybody who can prove ownership of a domain.
+The most accessible means of obtaining HTTPS certificates is using [Let's Encrypt](https://letsencrypt.org/). It provides free certificates to anybody who can prove ownership of a domain.
 Let's Encrypt offers a program called [certbot](https://certbot.eff.org/) to make acquiring certificates as striaght forward as possible.
 
 Assuming you have [certbot](https://certbot.eff.org/) installed, the following script will generate and configure the required certificates (notice the placeholders):

docs/self-hosted/install/database.md

@@ -38,4 +38,4 @@ This chart installs a MySQL database which gets Gitpod up and running but is not
     mysql:
       enabled: false
     ```
- 3. Do a `helm upgrade --install -f values.custom.yaml gitpod gitpod.io/gitpod` to apply the changes.
+ 3. Do a `helm upgrade --install -f values.custom.yaml gitpod gitpod.io/gitpod --version=0.7.0` to apply the changes.

docs/self-hosted/install/docker-registry.md

@@ -48,7 +48,7 @@ To connect to an existing Docker registry, perform the following steps:
     
     > This does not work for Google Cloud Registries because their login tokens are short-lived. See the [example](#example-google-cloud-registry-credentials) below on how to configure it.
 
- 3. Do a `helm upgrade --install -f values.custom.yaml gitpod gitpod.io/gitpod` to apply the changes.
+ 3. Do a `helm upgrade --install -f values.custom.yaml gitpod gitpod.io/gitpod --version=0.7.0` to apply the changes.
 
 Make sure the resulting JSON file contains the credentials (there should be an `auths` section containing them as base64 encoded string).
 

docs/self-hosted/install/install-on-aws-script.md

@@ -2,7 +2,7 @@
 url: /docs/self-hosted/latest/install/install-on-aws-script/
 ---
 
-> For this release (0.6.0, December 2019) the installers are broken. We're working in bringing those with the next release (January 2020).
+> Since the `0.6.0` release (December 2019) the installers are broken. We're working on bringing those back with one of the next releases.
 
 # Getting started with Gitpod on AWS
 
@@ -28,7 +28,7 @@ docker run --rm -it \
     -e AWS_ACCESS_KEY_ID \
     -e AWS_SECRET_ACCESS_KEY \
     -v "$PWD/awsinstall":"/workspace" \
-    gcr.io/gitpod-io/self-hosted/installer:latest aws
+    gcr.io/gitpod-io/self-hosted/installer:0.7.0 aws
 ```
 
 This will kickstart the installation process, authenticate with AWS and automatically set up your Gitpod deployment using Docker and Terraform.

docs/self-hosted/install/install-on-gcp-script.md

@@ -2,7 +2,7 @@
 url: /docs/self-hosted/latest/install/install-on-gcp-script/
 ---
 
-> For this release (0.6.0, December 2019) the installers are broken. We're working in bringing those with the next release (January 2020).
+> Since the `0.6.0` release (December 2019) the installers are broken. We're working on bringing those back with one of the next releases.
 
 # Getting started with Gitpod on GCP
 
@@ -20,7 +20,7 @@ mkdir -p $PWD/gpinstall
 docker run --rm -it \
     -v $PWD/gcloud:/root/.config/gcloud \
     -v $PWD/gpinstall:/workspace \
-    gcr.io/gitpod-io/self-hosted/installer:latest \
+    gcr.io/gitpod-io/self-hosted/installer:0.7.0 \
     gcp
 ```
 

docs/self-hosted/install/install-on-kubernetes.md

@@ -36,16 +36,28 @@ To install Gitpod in your Kubernetes cluster, follow these steps:
     ```console
     helm repo add gitpod.io https://charts.gitpod.io
 
-    helm install -f values.custom.yaml gitpod gitpod.io/gitpod
+    helm install -f values.custom.yaml gitpod gitpod.io/gitpod --version=0.7.0
     ```
 
-1. Run `kubectl get pods` and verify that all pods are in state `RUNNING`. If some are not, please see the [Troubleshooting Guide](../troubleshooting/).
-
 1. Configure [domain and https](../configure-ingress/).
 
+1. Run `kubectl get pods` and verify that all pods are in state `RUNNING`. If some are not, please see the [Troubleshooting Guide](../troubleshooting/).
+
 1. Go to [https://\<your-domain.com\>](https://\<your-domain.com\>) and follow the steps to complete the installation.
 
 
+## Upgrade
+
+ 1. Check the [Upgrade Guide](../upgrade/) and follow the steps outlined there.
+
+ 1. Run the update
+    ```console
+    helm install -f values.custom.yaml gitpod gitpod.io/gitpod --version=0.7.0
+    ```
+
+ 1. Run `kubectl get pods` and verify that all pods are in state `RUNNING`. If some are not, please see the [Troubleshooting Guide](../troubleshooting/).
+
+
 ## Recommended Configuration
 
 By default, 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:

docs/self-hosted/install/nodes.md

@@ -41,6 +41,6 @@ To do this:
         # The faster this location is (in terms of IO) the faster workspaces will initialize.
         hostWorkspaceArea: /mnt/disks/ssd0/workspaces
     ```
- 2. Do a `helm upgrade --install -f values.custom.yaml gitpod gitpod.io/gitpod` to apply the changes.
+ 2. Do a `helm upgrade --install -f values.custom.yaml gitpod gitpod.io/gitpod --version=0.7.0` to apply the changes.
 
     > Note that Helm does _not_ merge hierarchies in a single file. Please make sure there is only ever _one_ `components` hierarchy or the last one overwrites all previous values.

docs/self-hosted/install/oauth.md

@@ -46,7 +46,7 @@ Alternatively, you can configure it per Helm values file:
     ```
     Replace `CLIENT_ID` and `SECRET` with their respective values.
 
- 3. Do a `helm upgrade --install -f values.custom.yaml gitpod gitpod.io/gitpod` to apply the changes.
+ 3. Do a `helm upgrade --install -f values.custom.yaml gitpod gitpod.io/gitpod --version=0.7.0` to apply the changes.
 
 ## GitHub
 To authenticate your users with GitHub you need to create a [GitHub OAuth App](https://developer.github.com/apps/building-oauth-apps/creating-an-oauth-app/).

docs/self-hosted/install/storage.md

@@ -33,7 +33,7 @@ For more complex use case we recommend configuring more permanent means of persi
     minio:
       enabled: false
     ```
- 2. Redeploy Gitpod using `helm upgrade --install -f values.custom.yaml gitpod gitpod.io/gitpod` to apply the changes
+ 2. Redeploy Gitpod using `helm upgrade --install -f values.custom.yaml gitpod gitpod.io/gitpod --version=0.7.0` to apply the changes
 
     > Note that Helm does _not_ merge hierarchies in a single file. Please make sure there is only ever _one_ `components` hierarchy or the last one overwrites all previous values.
 
@@ -46,4 +46,4 @@ For more complex use case we recommend configuring more permanent means of persi
       secretKey: add-a-radom-secret-key-here
       # insert custom config here
     ```
- 3. Redeploy Gitpod using `helm upgrade --install -f values.custom.yaml gitpod gitpod.io/gitpod` to apply the changes
+ 3. Redeploy Gitpod using `helm upgrade --install -f values.custom.yaml gitpod gitpod.io/gitpod --version=0.7.0` to apply the changes

docs/self-hosted/install/troubleshooting.md

@@ -6,9 +6,9 @@ url: /docs/self-hosted/latest/install/troubleshooting/
 
 This section should solve all errors that might come up during installation of Gitpod.
 
-## `ws-daemon` is stuck in `Init: 0/1`
 
-### Diagnose   
+## 1. `ws-daemon` is stuck in `Init: 0/1`
+
 `kubectl describe pod ws-daemon-...` gives:
 `MountVolume.SetUp failed for volume "node-fs1" : hostPath type check failed: /run/containerd/io.containerd.runtime.v1.linux/k8s.io is not a directory`
 
@@ -27,4 +27,24 @@ This section should solve all errors that might come up during installation of G
           - <your path here>
     ```
 
-3. Do an `helm upgrade --install -f values.custom.yaml gitpod gitpod.io/gitpod` to apply the changes.
+ 3. Do an `helm upgrade --install -f values.custom.yaml gitpod gitpod.io/gitpod --version=0.7.0` to apply the changes.
+
+
+## 2. `helm install` fails with: "minio access key is required, please add a value to your values.yaml"
+
+Since `0.7.0` minio requires custom credentials to be configured.
+
+### Solution
+ 1. Follow the [Upgrade Guide](../upgrade/).
+
+
+## 3. After upgrade, the `minio` Pod is stuck in `ContainerCreating`
+
+This is caused by a bug in the minio Helm chart which blocks itself on updates.
+
+### Solution
+ 1. `kubectl scale deployments/minio --replicas=0`
+
+ 1. `kubectl scale deployments/minio --replicas=1`
+
+ 1. Wait until the pod comes up.

docs/self-hosted/install/workspaces.md

@@ -46,4 +46,4 @@ If you want to change the default sizing (~ 8GiB per workspace) you should
           controlPeriod: "15m"
     ```
 
- 2. Do a `helm upgrade --install -f values.custom.yaml gitpod gitpod.io/gitpod` to apply the changes.
+ 2. Do a `helm upgrade --install -f values.custom.yaml gitpod gitpod.io/gitpod --version=0.7.0` to apply the changes.