Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
Reference Architecture: Google Cloud Anthos and GDC Virtual on Dell PowerFlex
Executive summary Introduction Product overview Google Cloud Anthos Anthos on PowerFlex Anthos on VMware
Solution overview
Prerequisites
Physical design
VMware logical design
Deploying Anthos on VMware Anthos on bare metal Deploying Anthos on bare metal Deploying PowerFlex CSI on the Anthos cluster Deploying Anthos applications on the PowerFlex system Conclusion Appendix References

Prerequisites

Prerequisites

  • Deploying VMware-based Anthos on PowerFlex requires:

    • A fully configured and working PowerFlex system at RCM 3.6 or greater.
    • A Google Account, GCP Service Account, and a billing enabled GCP project. For more information, see Configuring your Google Cloud project.
    • At least one VMFS datastore with 2 TB capacity (based on a PowerFlex volume).
    • Ability to create required DNS entries.
    • A Layer 4 network load balancer. Default is MetalLB.
    • Plan IP addresses in three networks as required, before deployment.
    • Network access to Google Cloud APIs (*.googleapis.com).
    • For Google Anthos VMware based configuration and version compatibility information, see Anthos GKE on-prem Compatibility Matrix.

    For Google Anthos VMware based configuration and version compatibility information, see Anthos GKE on-prem Compatibility Matrix.

    Also, at least one outbound connection to Google Cloud APIs (*.googleapis.com) is required to complete the Anthos cluster registration and deployment processes. 

    Resource requirement for Anthos cluster

    The following tables provide details of CPU, RAM, and storage requirements for the admin workstation, admin cluster and user cluster:

    Table 2. Admin workstation

    Name

    vCPU

    Memory

    Storage

    Admin workstation

    4

    8 GiB 

    50 GiB

    Table 3.      Admin cluster

    Name

    vCPU

    Memory

    Storage

    Purpose

    Admin cluster control plane

    2

    4 GiB

    40 GiB

    Runs the control plane for the admin cluster.

    Add-on VMs

    4

    16 GiB

    40 GiB

    Runs add-ons for the admin cluster.

    User cluster control plane

    3

    5 GiB

    60 GiB

    Each user cluster has its own control plane that runs on a VM. The control plane VMs for a user cluster are nodes in the admin cluster. You can choose to create one or three control plane nodes for an individual user cluster.

    Table 4.      User cluster

    Name

    CPU

    Memory

    Storage

    Purpose

    User cluster worker nodes

    4

    8 GiB

    40 GiB

    A user cluster node is a virtual machine where your workloads run. When you create a user cluster, you decide how many nodes it should have. The resources required for your user cluster nodes depend on the workloads you intend to run.


    Scalability limits

    Google Anthos applies the following limits: 

    Note: These limits can be affected by vSphere configuration and hardware:

    • For each admin cluster, you can deploy a maximum of 20 user clusters.
    • For each user cluster:
      • You can create a minimum of three nodes.
      • You can create a maximum of 250 nodes.
      • You can create a maximum of 7500 pods:
        • Generally, each node includes an average of 30 pods. However, when Google Cloud's operations suite is enabled, each node includes an average of 20 pods.
        • Each pod can consist of one or more containers.
    • For each node, you can create a maximum of 110 pods. This includes pods running add-on services.
    • For bundled load balancing mode, you can create a maximum of 500 Load Balancer services. For more information, see Scalability limits.