Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 19. Configuring for GCE

19.1. Overview

OpenShift Container Platform can be configured to access a Google Compute Engine (GCE) infrastructure, including using GCE volumes as persistent storage for application data. After GCE is configured properly, some additional configurations will need to be completed on the OpenShift Container Platform hosts.

19.2. Configuring Masters

You can set the GCE configuration on your OpenShift Container Platform master hosts in two ways:

19.2.1. Configuring OpenShift Container Platform Masters for GCE with Ansible

During advanced installations, GCE can be configured using the openshift_cloudprovider_kind parameter, which is configurable in the inventory file.

Example GCE Configuration with Ansible

Copy to Clipboard Toggle word wrap 
# Cloud Provider Configuration
#
  openshift_cloudprovider_kind=gce

Note

When Ansible configures GCE, the following files are created for you:

  • /etc/origin/cloudprovider/gce.conf
  • /etc/origin/master/master-config.yaml
  • /etc/origin/node/node-config.yaml

The advanced installation configures multizone support by default. If you want single-zone support, edit the /etc/origin/cloudprovider/gce.conf as shown in Configuring Multizone Support in a GCE Deployment.

19.2.2. Manually Configuring OpenShift Container Platform Masters for GCE

To configure the OpenShift Container Platform masters for GCE:

  1. Edit or create the master configuration file (/etc/origin/master/master-config.yaml by default) on all masters and update the contents of the apiServerArguments and controllerArguments sections:

    Copy to Clipboard Toggle word wrap 
    kubernetesMasterConfig:
  ...
  apiServerArguments:
    cloud-provider:
      - "gce"
    cloud-config:
      - "/etc/origin/cloudprovider/gce.conf"
  controllerArguments:
    cloud-provider:
      - "gce"
    cloud-config:
      - "/etc/origin/cloudprovider/gce.conf"
    Important

    When triggering a containerized installation, only the directories of /etc/origin and /var/lib/origin are mounted to the master and node container. Therefore, master-config.yaml should be in /etc/origin/master instead of /etc/.

  2. Start or restart the OpenShift Container Platform services:

    Copy to Clipboard Toggle word wrap 
    # systemctl restart atomic-openshift-master

19.3. Configuring Nodes

To configure the OpenShift Container Platform nodes for GCE:

  1. Edit or create the node configuration file (/etc/origin/node/node-config.yaml by default) on all nodes and update the contents of the kubeletArguments section:

    Copy to Clipboard Toggle word wrap 
    kubeletArguments:
 cloud-provider:
    - "gce"
  cloud-config:
    - "/etc/origin/cloudprovider/gce.conf"

Currently, the nodeName must match the instance name in GCE in order for the cloud provider integration to work properly. The name must also be RFC1123 compliant.

Important

When triggering a containerized installation, only the directories of /etc/origin and /var/lib/origin are mounted to the master and node container. Therefore, node-config.yaml should be in /etc/origin/node instead of /etc/.

  1. Start or restart the OpenShift Container Platform services all nodes.

    Copy to Clipboard Toggle word wrap 
    # systemctl restart atomic-openshift-node

19.4. Configuring Multizone Support in a GCE Deployment

If manually congifuring GCE, multizone support is not configured by default.

Note

The advanced installation configures multizone support by default.

If you want multizone support:

  1. Edit or create a /etc/origin/cloudprovider/gce.conf file on all of your OpenShift Container Platform hosts, both masters and nodes.

  2. Add the following contents:

    Copy to Clipboard Toggle word wrap 
    [Global]
multizone = true

To return to single-zone support, set the multizone value to false.

19.5. Applying Configuration Changes

Start or restart OpenShift Container Platform services on all master and node hosts to apply your configuration changes:

Copy to Clipboard Toggle word wrap 
# systemctl restart atomic-openshift-master
# systemctl restart atomic-openshift-node

Switching from not using a cloud provider to using a cloud provider produces an error message. Adding the cloud provider tries to delete the node because the node switches from using the hostname as the externalID (which would have been the case when no cloud provider was being used) to using the GCE instance-id (which is what the GCE cloud provider specifies). To resolve this issue:

  1. Log in to the CLI as a cluster administrator.

  2. Check and backup existing node labels:

    Copy to Clipboard Toggle word wrap 
    $ oc describe node <node_name> | grep -Poz '(?s)Labels.*\n.*(?=Taints)'

  3. Delete the nodes:

    Copy to Clipboard Toggle word wrap 
    $ oc delete node <node_name>

  4. On each node host, restart the OpenShift Container Platform service.

    Copy to Clipboard Toggle word wrap 
    $ systemctl restart atomic-openshift-node
  5. Add back any labels on each node that you previously had.
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat, Inc.