diff --git a/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/cloud-providers/_index.md b/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/cloud-providers/_index.md
index ee5c9c2af7f..70dc4464f42 100644
--- a/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/cloud-providers/_index.md
+++ b/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/cloud-providers/_index.md
@@ -26,6 +26,10 @@ For details on enabling the Amazon cloud provider, refer to [this page.]({{}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/cloud-providers/azure)
+### Setting up the GCE Cloud Provider
+
+For details on enabling the Google Compute Engine cloud provider, refer to [this page.]({{}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/cloud-providers/gce)
+
### Setting up a Custom Cloud Provider
The `Custom` cloud provider is available if you want to configure any [Kubernetes cloud provider](https://kubernetes.io/docs/concepts/cluster-administration/cloud-providers/).
diff --git a/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/cloud-providers/gce/_index.md b/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/cloud-providers/gce/_index.md
index d5f13a993f8..32980b2e40e 100644
--- a/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/cloud-providers/gce/_index.md
+++ b/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/cloud-providers/gce/_index.md
@@ -3,9 +3,7 @@ title: Setting up the Google Compute Engine Cloud Provider
weight: 3
---
-In this section, you'll learn how to enable the Google Compute Engine (GCE) cloud provider for provisioning custom clusters in Rancher. A custom cluster is one in which Rancher installs Kubernetes on existing nodes.
-
-These steps are required for provisioning GCE Kubernetes clusters that include Windows nodes.
+In this section, you'll learn how to enable the Google Compute Engine (GCE) cloud provider for custom clusters in Rancher. A custom cluster is one in which Rancher installs Kubernetes on existing nodes.
The official Kubernetes documentation for the GCE cloud provider is [here.](https://kubernetes.io/docs/concepts/cluster-administration/cloud-providers/#gce)
@@ -17,18 +15,18 @@ If you are using Calico,
1. Click **Edit as YAML,** and enter the following configuration:
```yaml
rancher_kubernetes_engine_config:
- cloud_provider:
+ cloud_provider: // indent 2 spaces than `rancher_kubernetes_engine_config`
name: gce
- customCloudProvider: |-
- [Global]
- project-id=
- network-name=
- subnetwork-name=
- node-instance-prefix=
- node-tags=
- network:
+ customCloudProvider: |-
+ [Global]
+ project-id=
+ network-name=
+ subnetwork-name=
+ node-instance-prefix=
+ node-tags=
+ network:
options:
- calico_cloud_provider: "gce"
+ calico_cloud_provider: "gce"
plugin: "calico"
```
@@ -38,18 +36,17 @@ If you are using Canal or Flannel,
1. Click **Edit as YAML,** and enter the following configuration:
```yaml
rancher_kubernetes_engine_config:
- cloud_provider:
+ cloud_provider:
name: gce
- customCloudProvider: |-
- [Global]
- project-id=
- network-name=
- subnetwork-name=
- node-instance-prefix=
- node-tags=
- services:
- kube_controller:
- extra_args:
- configure-cloud-routes: true # we need to allow
- # the cloud provider to configure the routes for the hosts
+ customCloudProvider: |-
+ [Global]
+ project-id=
+ network-name=
+ subnetwork-name=
+ node-instance-prefix=
+ node-tags=
+ services:
+ kube_controller:
+ extra_args:
+ configure-cloud-routes: true # we need to allow the cloud provider configure the routes for the hosts
```
\ No newline at end of file