Ensure that you meet the following requirements and prerequisites before installing VMware Tanzu Operations Manager on Google Cloud Platform (GCP).

You can install Tanzu Operations Manager on GCP with either the VMware Tanzu Application Service for VMs (TAS for VMs) or VMware Tanzu Kubernetes Grid Integrated Edition (TKGI) runtime. There are resource requirements specific to each runtime. Ensure that you meet the requirements for your runtime and the requirements specific to GCP before installing Tanzu Operations Manager on GCP.

Requirements

This section lists the following resource requirements for installing Tanzu Operations Manager on GCP:

Tanzu Operations Manager Resource requirements

This section lists resource requirements for installing Tanzu Operations Manager on GCP. It includes links to general resource requirements for both the TAS for VMs and TKGI runtimes.

See one of the following topics, depending on the runtime you plan to install using Tanzu Operations Manager:

GCP resource requirements

The following are GCP-specific resource requirements for installing Tanzu Operations Manager on GCP:

Installing Tanzu Operations Manager on GCP requires a minimum of the following VM instance limits in your GCP account. The number of VMs required depends on the number of tiles and availability zones you plan to deploy. The following VM guidelines apply to the TAS for VMs and Small Footprint TAS for VMs runtimes:

  • TAS for VMs: At a minimum, a new GCP deployment requires the following custom VMs for TAS for VMs and Tanzu Operations Manager:

    VM count vCPU count per VM RAM (GB)
    28 1 1
    2 2 1
    3 1 2
    4 2 4
    3 2 8
    3 4 16

    If you are deploying a test or sandbox deployment that does not require high availability, then you can scale down the number of VM instances in your deployment. For more information, see Scaling TAS for VMs.

  • Small Footprint TAS for VMs: At a minimum, a new GCP deployment requires the following VMs to run Small Footprint TAS for VMs:

    VM type VM count vCPU count per VM RAM (GB) Notes
    Small footprint TAS for VMs micro 11 1 1 Add 1 to VM count if using HAProxy
    small 3 1 2
    highcpu 1 2 2
    xlarge.disk 1 4 16
    xlarge 1 4 16
    medium.mem 1 1 6
    large.disk 1 2 8
    Tanzu Operations Manager large.disk 1 2 8
    large.cpu 4 4 4

  • TKGI: See GCP Prerequisites and Resource Requirements.

  • (TAS for VMs-only) Your GCP project must have sufficient quota to deploy all the VMs needed to install Tanzu Operations Manager with TAS for VMs. For a list of suggested quotas, see Recommended GCP quotas.

Prerequisites

To install Tanzu Operations Manager on GCP, you must do the following:

  • Install the Google Cloud SDK on your machine and authenticate it to your GCP account. To download the Google Cloud SDK, see Google Cloud SDK.

  • Increase or remove the VM instance limits in your GCP account. For VM instance requirements, see GCP Resource Requirements, above.

  • Update your GCP account with the following required permissions:

    • The following permissions are required to create firewalls, networks, load balancers, and other resources:
      • Compute Engine, then Compute Instances Admin (beta)
      • Compute Engine, then Compute Network Admin
      • Compute Engine, then Compute Security Admin
    • To use Google Cloud Storage (GCS) for Cloud Controller file storage, the following permission is required to create buckets:
      • Storage, then Storage Admin
    • To use Cloud DNS, the following permission is required to add and modify DNS entries:
      • Project, then Owner

  • Create an SSL certificate for your Tanzu Operations Manager domain.
    To deploy Tanzu Operations Manager to a production environment, you must obtain a certificate from a certificate authority. VMware recommends using a self-signed certificate generated by Tanzu Operations Manager for development and testing purposes only.

  • Assign administrative rights to a domain for Tanzu Operations Manager. You need to be able to add wildcard records to this domain.

  • Create a wildcard DNS record that points to your router or load balancer. Alternatively, you can use a service such as xip.io; for example, 203.0.113.0.xip.io. Then create at least one wildcard TLS certificate that matches the DNS record you configured.
    With a wildcard DNS record, every hostname in your domain resolves to the IP address of your router or load balancer. For example, if you create a DNS record *.example.com pointing to your router, every app deployed to the example.com domain resolves to the IP address of your router.

  • Create one or more NTP servers, if the NTP servers are not already provided by your GCP project.

  • Install the most recent version of one of the following CLIs, depending on your runtime:

  • TAS for VMs-only:

  • (Optional) (TAS for VMs-only) Configure external storage. VMware recommends using external storage if possible. For more information about how file storage location affects platform performance and stability during upgrades, see Configure file storage in Configuring TAS for VMs for Upgrades.

    • (Optional) (TAS for VMs and Tanzu Operations Manager-only) Configure external databases. VMware recommends using external databases in production deployments for BOSH Director and TAS for VMs. An external database must be configured to use the UTC timezone.

  • (Optional) (TAS for VMs and Tanzu Operations Manager-only) Configure external user stores. When you deploy Tanzu Operations Manager, you can select a SAML user store for Tanzu Operations Manager or a SAML or LDAP user store for TAS for VMs, to integrate existing user accounts.

Install Tanzu Operations Manager on GCP

You can install Tanzu Operations Manager on GCP.

To install Tanzu Operations Manager on GCP, see Installing Tanzu Operations Manager on GCP

Additional resources

The following are additional resources related to installing Tanzu Operations Manager on GCP:

check-circle-line exclamation-circle-line close-line
Scroll to top icon