PLEASE NOTE: This document applies to v0.2 version and not to the latest release v0.5

Documentation for other releases can be found by using the version selector in the top right of any doc page.

Deploying a WordPress Workload on GCP

This guide will walk you through how to use Crossplane to deploy a stateful workload in a portable way to GCP. In this environment, the following components will be dynamically provisioned and configured during this guide:


Before starting this guide, you should have already configured your GCP account for usage by Crossplane.

You should have a crossplane-gcp-provider-key.json file on your local filesystem, preferably at the root of where you cloned the Crossplane repo.

Administrator Tasks

This section covers the tasks performed by the cluster or cloud administrator, which includes:

Note: all artifacts created by the administrator are stored/hosted in the crossplane-system namespace, which has restricted access, i.e. Application Owner(s) should not have access to them.

For the next steps, make sure your kubectl context points to the cluster where Crossplane was deployed.

To recap the operations that we just performed as the administrator:

Application Developer Tasks

This section covers the tasks performed by the application developer, which includes:

Let’s begin deploying the workload as the application developer:

At this point, you should see the setup page for WordPress in your web browser.

Clean Up

Once you are done with this example, you can clean up all its artifacts with the following commands: