Setting up Cloud Run for Anthos on VMware

This guide shows you how to set up Anthos clusters on VMware (GKE on-prem) with Cloud Run for Anthos enabled.

Note that installing Cloud Run for Anthos on VMware installs Knative Serving into the cluster to connect and manage your stateless workloads.

Before you begin

  1. This task assumes that you have active Anthos clusters on VMware (GKE on-prem). Learn how to create Anthos clusters on VMware.

    For information about Anthos, see Anthos Pricing.

  2. Sign in to your Google Cloud account. If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.
  3. In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

    Go to project selector

  4. Make sure that billing is enabled for your Google Cloud project.

  5. In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

    Go to project selector

  6. Make sure that billing is enabled for your Google Cloud project.

Setting up the command-line environment

Set up the gcloud CLI and kubectl for Cloud Run for Anthos on VMware:

  1. Install and initialize the Google Cloud CLI.

  2. Set the default Google Cloud project that is used by the Google Cloud CLI to the Google Cloud project that you just created:

    gcloud config set project PROJECT-ID

    Replace PROJECT_ID with the ID of your Google Cloud project.

  3. Install the kubectl command-line tool:

    gcloud components install kubectl
  4. Update installed gcloud CLI components:

    gcloud components update

Installing Cloud Run for Anthos on VMware

You can install Cloud Run for Anthos while creating new Anthos clusters on VMware by setting the cloudrun configuration in the config.yaml file:

cloudrun:
  enabled: true

Setting up the Google Cloud console

When using the Google Cloud console, login to the cluster. If you are using a Kubernetes Service Account, be sure to add the cluster-admin role to that Service Account.

What's next