Configuring for GCE | Installation and Configuration

Overview
Configuring Masters
- Configuring OpenShift Origin Masters for GCE with Ansible
- Manually Configuring OpenShift Origin Masters for GCE
Configuring Nodes
Configuring Multizone Support in a GCE Deployment

Overview

OpenShift Origin 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 Origin hosts.

Configuring Masters

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

Using Ansible and the advanced installation tool.
Manually by modifying the master-config.yaml file.

Configuring OpenShift Origin 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

# Cloud Provider Configuration
#
  openshift_cloudprovider_kind=gce

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.

Manually Configuring OpenShift Origin Masters for GCE

To configure the OpenShift Origin masters for GCE:

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:

kubernetesMasterConfig:
  ...
  apiServerArguments:
    cloud-provider:
      - "gce"
    cloud-config:
      - "/etc/origin/cloudprovider/gce.conf"
  controllerArguments:
    cloud-provider:
      - "gce"
    cloud-config:
      - "/etc/origin/cloudprovider/gce.conf"

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/.

Start or restart the OpenShift Origin services:
```
# systemctl restart origin-master
```

Configuring Nodes

To configure the OpenShift Origin nodes for GCE:

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:

kubeletArguments:
 cloud-provider:
    - "gce"
  cloud-config:
    - "/etc/origin/cloudprovider/gce.conf"

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/.

Start or restart the OpenShift Origin services all nodes.
```
# systemctl restart origin-node
```

Configuring Multizone Support in a GCE Deployment

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

The advanced installation configures multizone support by default.

If you want multizone support:

Edit or create a /etc/origin/cloudprovider/gce.conf file on all of your OpenShift Origin hosts, both masters and nodes.
Add the following contents:
```
[Global]
multizone = true
```
Start or restart the OpenShift Origin services on the master and all nodes.
```
# systemctl restart origin-master
# systemctl restart origin-node
```

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