Read through the following checklist before activating Tanzu.

  • You must be logged into the VMC console as a user with a VMC service role of Administrator.
  • To qualify for Tanzu Kubernetes Grid activation, your SDDC must meet the following criteria:
    • Your SDDC must be running version 1.16 or later.
    • Your SDDC must have at least one conventional cluster with either three or four hosts based on the rack node type and no deployed customer workloads.
      The following table provides information on the minimum and maximum nodes required based on the rack node type.
      R2
      Node Type CPUs Memory Sockets Minimum nodes without WCP Minimum nodes with WCP
      G1s.small 24 256 1 3 4
      M1s.medium 24 384 1 3 4
      M1d.medium 56 768 2 3 3
      X1d.xLarge 48 1536 2 3 3
      M1d.xLarge 56 768 2 3 3
  • Ensure that the range of IP addresses that you choose for each CIDR block does not overlap the workload network address range of other Tanzu clusters in your SDDC, the SDDC Management or Compute networks, or your on-premises networks. For a complete list of IPv4 addresses reserved by VMware Cloud on Dell EMC, see Reserved Network Addresses. These CIDR blocks cannot be changed after you activate Tanzu Kubernetes Grid.
  • Your CIDR blocks must be in one of the "private address space" blocks defined by RFC 1918 (10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16). CIDR blocks of size 16, 20, 23, or 26 are supported.
  • You must be ready with the following CIDR ranges.
    Service CIDR An abstract way to expose an application running on a set of Pods as a network service. Addresses allocated to Tanzu supervisor services. Cannot overlap with the Namespace Network CIDR, Ingress CIDR, or Egress CIDR.

    This CIDR should have a span of at least /23 to provide adequate capacity for your Tanzu Kubernetes Grid workloads. Consider a span of /16 or /12.
    Namespace Network CIDR (Pod CIDR) Addresses allocated to namespace segments. Cannot overlap with the SDDC Management or Compute subnets.

    This CIDR should have a span of at least /23 to provide adequate capacity for your Tanzu Kubernetes Grid workloads. Consider a span of /16 or /12.
    Ingress CIDR Inbound traffic through load-balancers to containers. Cannot overlap with the SDDC Management or Compute subnets.

    The system creates a NAT address from this pool for each Tanzu Kubernetes Grid namespace, so a span of /24 or /26 should be adequate.
    Egress CIDR SNATted outbound traffic from containers and guest clusters cannot overlap with the SDDC Management or Compute subnets.

    The system allocates an SNAT IP address from this pool for each Tanzu Kubernetes Grid namespace, so a span of /24 or /26 should be adequate.
  • When configuring uplinks, if you selected your routing protocol as:
    • Static: Add two static routes on your router pointing towards VMware Cloud on Dell for both ingress and egress CIDRs
    • BGP: Do not add static routes for egress or ingress CIDRs on your router as these routes are advertised by VMware Cloud on Dell TORs over BGP