diff --git a/README.md b/README.md
index 000a1bab1..8d48a8556 100644
--- a/README.md
+++ b/README.md
@@ -33,8 +33,8 @@ covers individual newer features separately.
 
 | Platform             | Kubernetes version | ArangoDB version | ArangoDB K8s Operator Version | State | Production ready | Remarks               |
 |----------------------|--------------------|------------------|-------------------------------|-------|------------------|-----------------------|
-| Google GKE           | 1.10               | >= 3.3.13        |                               | Runs  | Yes              | Don't use micro nodes |
-| Google GKE           | 1.11               | >= 3.3.13        |                               | Runs  | Yes              | Don't use micro nodes |
+| Google GKE           | 1.12               | >= 3.3.13        |                               | Runs  | Yes              | Don't use micro nodes |
+| Google GKE           | 1.13               | >= 3.3.13        |                               | Runs  | Yes              | Don't use micro nodes |
 | Amazon EKS           | 1.11               | >= 3.3.13        |                               | Runs  | Yes              |                       |
 | Pivotal PKS          | 1.11               | >= 3.3.13        |                               | Runs  | Yes              |                       |
 | IBM Cloud            | 1.11               | >= 3.4.5         |          >= 0.3.11            | Runs  | Yes              |                       |
diff --git a/docs/Manual/Tutorials/Kubernetes/GKE.md b/docs/Manual/Tutorials/Kubernetes/GKE.md
index 5624036dd..52f1813fb 100644
--- a/docs/Manual/Tutorials/Kubernetes/GKE.md
+++ b/docs/Manual/Tutorials/Kubernetes/GKE.md
@@ -40,59 +40,17 @@ permissions, you need "administrator" permissions.
 
 To get these permissions, do the following.
 
-Prepare your `~/.kube/config` with the following content:
-
-```yaml
-apiVersion: v1
-clusters:
-- cluster:
-    certificate-authority-data:
-    server: https://
-  name: my_cluster
-contexts:
-- context:
-    cluster: my_cluster
-    user: my_cluster
-  name: my_cluster
-current-context: my_cluster
-kind: Config
-preferences: {}
-users:
-- name: my_cluster
-  user:
-    username: admin
-    password:
-```
-
-Click on the `Edit` button (pencil image) next to your cluster.
-This will lead you to the following page.
-
-![edit cluster](./gke-edit-cluster.png)
-
-Copy the `Endpoint` IP address and paste it after `server: https://`.
-
-The click on `Show credentials`.
-The following popup will appear.
-
-![show credentials](./gke-show-credentials.png)
-
-Copy the `Password` and paste it after `password:`.
-
-Close the popup and then return to the cluster list.
-
 Click on `Connect` next to your cluster.
 The following popup will appear.
 
 ![connect to cluster](./gke-connect-to-cluster.png)
 
 Click on `Run in Cloud Shell`.
+
 It will take some time to launch a shell (in your browser).
 
 Once ready, run the `gcloud` command that is already prepare in your commandline.
 
-The run `cat ~/.kube/config` and copy the line that starts with `certificate-authority-data:`.
-Override the corresponding line in your local `~/.kube.config` file.
-
 You should now be able to access your cluster using `kubectl`.
 
 To verify try a command like:
diff --git a/docs/Manual/Tutorials/Kubernetes/gke-edit-cluster.png b/docs/Manual/Tutorials/Kubernetes/gke-edit-cluster.png
deleted file mode 100644
index cd503e53c..000000000
Binary files a/docs/Manual/Tutorials/Kubernetes/gke-edit-cluster.png and /dev/null differ
diff --git a/docs/Manual/Tutorials/Kubernetes/gke-show-credentials.png b/docs/Manual/Tutorials/Kubernetes/gke-show-credentials.png
deleted file mode 100644
index bf70bbd0f..000000000
Binary files a/docs/Manual/Tutorials/Kubernetes/gke-show-credentials.png and /dev/null differ