Skip to content

README.md

Latest commit

 

History

History
66 lines (44 loc) · 2.35 KB

README.md

File metadata and controls

66 lines (44 loc) · 2.35 KB

Cloud

Folder structure

The folder contains the following top directories:

└── cloud
    ├── providers
    │   ├── base
    │   ├── dev
    │   ├── prod
    │   └── staging
    └── resources
        ├── base
        ├── dev
        ├── prod
        └── staging

Prerequisites

  • A Kubernetes cluster with at least 6 GB of RAM permissions to create pods and secrets in the Kubernetes cluster
  • Helm version v3.2.0 or later
  • A GCP account with permissions to create a storage bucket
  • GCP account keys
  • GCP Project ID

Provision a GKE cluster

Steps to provision a Crossplane cluster so that it can manage GKE resources.

1. Install the GCP provider

A provider installs their own Kubernetes Custom Resource Definitions (CRDs). These CRDs allow you to create GCP resources directly inside Kubernetes.

You can view the new CRDs with kubectl get crds. Every CRD maps to a unique GCP service Crossplane can provision and manage.

2. Create the Kubernetes secret for GCP

The provider requires credentials to create and manage GCP resources. Providers use a Kubernetes Secret to connect the credentials to the provider.

For basic user authentication, use a Google Cloud service account JSON file. See the GCP Docs.

Save the JSON file as gcp-credentials.json. Its base64 encoded value is the one that will go to the secret.

3. Create a ProviderConfig

A ProviderConfig customizes the settings of the GCP Provider.

4. Create a Managed Resource (MR)

Now that the provider is configured we can create Kubernetes resources so Crossplane defines the required state in our target cloud provider.

The ./resources/ folder has some managed resource examples.

Resources

GCP Quickstart