Tanzu for Kubernetes Operations simplifies operating Kubernetes for multi-cloud deployment by centralizing management and governance for clusters and teams across on-premises, public clouds, and edge. It delivers an open source aligned Kubernetes distribution with consistent operations and management to support infrastructure and app modernization.
This document describes a reference design for deploying VMware Tanzu for Kubernetes Operations on vSphere backed by vSphere Networking (VDS).
The following reference design is based on the architecture and components described in VMware Tanzu for Kubernetes Operations Reference Architecture.
The following table provides the component versions and interoperability matrix supported with the reference design:
|Tanzu Kubernetes Grid||1.5.1|
|VMware vSphere ESXi||7.0 U2|
|VMware vCenter (VCSA)||7.0 U2 and later|
|VMware vSAN||7.0 U2 and later|
|NSX Advanced LB||20.1.7|
For the latest information, see VMware Product Interoperability Matrix.
VMware Tanzu Kubernetes Grid (TKG) provides organizations with a consistent, upstream-compatible, regional Kubernetes substrate that is ready for end-user workloads and ecosystem integrations. You can deploy Tanzu Kubernetes Grid across software-defined datacenters (SDDC) and public cloud environments, including vSphere, Microsoft Azure, and Amazon EC2.
Tanzu Kubernetes Grid comprises the following components:
Management Cluster - A management cluster is the first element that you deploy when you create a Tanzu Kubernetes Grid instance. The management cluster is a Kubernetes cluster that performs the role of the primary management and operational center for the Tanzu Kubernetes Grid instance. The management cluster is purpose-built for operating the platform and managing the lifecycle of Tanzu Kubernetes clusters.
Cluster API - Tanzu Kubernetes Grid functions through the creation of a management Kubernetes cluster which houses Cluster API. The Cluster API then interacts with the infrastructure provider to service workload Kubernetes cluster lifecycle requests.
Tanzu Kubernetes Cluster - Tanzu Kubernetes clusters are the Kubernetes clusters in which your application workloads run. These clusters are also referred to as workload clusters. Tanzu Kubernetes clusters can run different versions of Kubernetes, depending on the needs of the applications they run.
Shared Service Cluster - Each Tanzu Kubernetes Grid instance can only have one shared services cluster. You will deploy this cluster only if you intend to deploy shared services such as Contour and Harbor.
Tanzu Kubernetes Cluster Plans - A cluster plan is a blueprint that describes the configuration with which to deploy a Tanzu Kubernetes cluster. It provides a set of configurable values that describe settings like the number of control plane machines, worker machines, VM types, and so on. This release of Tanzu Kubernetes Grid provides two default templates, dev and prod.
Tanzu Kubernetes Grid Instance - A Tanzu Kubernetes Grid instance is the full deployment of Tanzu Kubernetes Grid, including the management cluster, the workload clusters, and the shared services cluster that you configure.
Tanzu CLI - A command-line utility that provides the necessary commands to build and operate Tanzu management and Tanzu Kubernetes clusters.
Bootstrap Machine - The bootstrap machine is the laptop, host, or server on which you download and run the Tanzu CLI. This is where the initial bootstrapping of a management cluster occurs before it is pushed to the platform where it will run.
Tanzu Kubernetes Grid Installer - The Tanzu Kubernetes Grid installer is a graphical wizard that you launch by running the
tanzu management-cluster create --ui command. The installer wizard runs locally on the bootstrap machine and provides a user interface to guide you through the process of deploying a management cluster.
Tanzu Kubernetes Grid integrates with shared datastores available in the vSphere infrastructure. The following types of shared datastores are supported:
Tanzu Kubernetes Grid Cluster Plans can be defined by operators to use a certain vSphere datastore when creating new workload clusters. All developers then have the ability to provision container-backed persistent volumes from that underlying datastore.
Tanzu Kubernetes Grid is agnostic to which option you choose. For Kubernetes stateful workloads, Tanzu Kubernetes Grid installs the vSphere Container Storage interface (vSphere CSI) to automatically provision Kubernetes persistent volumes for pods.
VMware vSAN is a recommended storage solution for deploying Tanzu Kubernetes Grid clusters on vSphere.
|Decision ID||Design Decision||Design Justification||Design Implications|
|TKO-STG-001||Use vSAN storage for TKO||vSAN supports NFS volumes in ReadWriteMany access modes.||vSAN File Services need to be configured to leverage this. vSAN File Service is available only in vSAN Enterprise and Enterprise Plus editions|
While the default vSAN storage policy can be used, administrators should evaluate the needs of their applications and craft a specific vSphere Storage Policy. vSAN storage policies describe classes of storage (For example, SSD or NVME) along with quotas for your clusters.
A Tanzu Kubernetes cluster provisioned by Tanzu Kubernetes Grid supports two Container Network Interface (CNI) options:
Both are open-source software that provides networking for cluster pods, services, and ingress.
When you deploy a Tanzu Kubernetes cluster using Tanzu Mission Control or Tanzu CLI, Antrea CNI is automatically enabled in the cluster.
Tanzu Kubernetes Grid also supports Multus CNI which can be installed through Tanzu user-managed packages. Multus CNI lets you attach multiple network interfaces to a single pod and associate each with a different address range.
To provision a Tanzu Kubernetes cluster using a non-default CNI, see the following instructions:
Each CNI is suitable for a different use case. The following table lists some common use cases for the three CNIs that Tanzu Kubernetes Grid supports. This table will help you with information on selecting the right CNI in your Tanzu Kubernetes Grid implementation.
|CNI||Use Case||Pros and Cons|
Enable Kubernetes pod networking with IP overlay networks using VXLAN or Geneve for encapsulation. Optionally encrypt node-to-node communication using IPSec packet encryption.
Antrea supports advanced network use cases like kernel bypass and network service mesh.
- Provides an option to configure egress IP pool or static egress IP for Kubernetes workloads.
Calico is used in environments where factors like network performance, flexibility, and power are essential.
For routing packets between nodes, Calico leverages the BGP routing protocol instead of an overlay network. This eliminates the need to wrap packets with an encapsulation layer resulting in increased network performance for Kubernetes workloads.
- Support for network policies
- High network performance
- SCTP support
- No multicast support
|Multus||Multus CNI provides multiple interfaces per each Kubernetes pod. Using Multus CRDs, you can specify which pods get which interfaces and allow different interfaces depending on the use case.||
- Separation of data/control planes.
- Separate security policies can be used for separate interfaces.
- Supports SR-IOV, DPDK, OVS-DPDK, and VPP workloads in Kubernetes with both cloud native and NFV based applications in Kubernetes.
Tanzu Kubernetes Grid on vSphere can be deployed on various networking stacks including
Note: The scope of this document is limited to vSphere Networking.
Tanzu Kubernetes Grid when deployed on the vSphere networking uses the distributed port groups to provide connectivity to Kubernetes control plane VMs, worker nodes, services, and applications. All hosts from the cluster where Tanzu Kubernetes clusters are deployed are connected to the distributed switch that provides connectivity to the Kubernetes environment.
Tanzu Kubernetes Grid leverages NSX Advanced Load Balancer to provide L4 load balancing for the Tanzu Kubernetes Clusters Control-Plane HA and L7 ingress to the applications deployed in the Tanzu Kubernetes clusters. Users access the applications by connecting to the virtual IP address (VIP) of the applications provisioned by NSX Advanced Load Balancer.
NSX Advanced Load Balancer is deployed in Write Access Mode in the vSphere environment. This mode grants NSX Advanced Load Balancer Controller full write access to the vCenter which helps in automatically creating, modifying, and removing service engines (SEs) and other resources as needed to adapt to changing traffic needs. The core components of NSX Advanced Load Balancer are as follows:
ConfigMaprequired for the AKO controller and other artifacts.
Tanzu Kubernetes Grid management clusters have an AKO operator installed out of the box during cluster deployment. By default, a Tanzu Kubernetes Grid management cluster has a couple of AkoDeploymentConfig created which dictates when and how AKO pods are created in the workload clusters. For more information, see AKO Operator documentation.
Each environment configured in NSX Advanced Load Balancer is referred to as a cloud. Each cloud in NSX Advanced Load Balancer maintains networking and NSX Advanced Load Balancer Service Engine settings. The cloud is configured with one or more VIP networks to provide IP addresses to load balancing (L4 or L7) virtual services created under that cloud.
The virtual services can span across multiple service engines if the associated Service Engine Group is configured in the Active/Active HA mode. A service engine can belong to only one Service Engine group at a time.
IP address allocation for virtual services can be over DHCP or using NSX Advanced Load Balancer in-built IPAM functionality. The VIP networks created or configured in NSX Advanced Load Balancer are associated with the IPAM profile.
For the deployment of Tanzu Kubernetes Grid in the vSphere environment, it is required to build separate networks for the Tanzu Kubernetes Grid management cluster and workload clusters, NSX Advanced Load Balancer management, cluster-VIP network for control plane HA, Tanzu Kubernetes Grid management VIP or data network, and Tanzu Kubernetes Grid workload data or VIP network.
The network reference design can be mapped into this general framework.
This topology enables the following benefits:
As per the defined architecture, the list of required networks follows:
|Network Type||DHCP Service||
Description & Recommendations
|NSX ALB Management Network||Optional||
NSX ALB controllers and SEs will be attached to this network.
DHCP is not a mandatory requirement on this network as NSX ALB can take care of IPAM.
|TKG Management Network||Yes||Control plane and worker nodes of TKG management cluster and shared service clusters will be attached to this network.
Creating shared service cluster on a separate network is also supported.
|TKG Workload Network||Yes||Control plane and worker nodes of TKG workload clusters will be attached to this network.|
|TKG Cluster VIP/Data Network||No||Virtual services for control plane HA of all TKG clusters (management, shared service, and workload).
Reserve sufficient IP addresses depending on the number of TKG clusters planned to be deployed in the environment. NSX Advanced Load Balancer takes care of IPAM on this network.
|TKG Management VIP/Data Network||No||Virtual services for all user-managed packages (such as Contour, Harbor, Contour, Prometheus, Grafana) hosted on the Shared service cluster. For more information, see User-Managed Packages.|
|TKG Workload VIP/Data Network||No||Virtual services for all applications are hosted on the workload clusters.
Reserve sufficient IP addresses depending on the number of applications that are planned to be hosted on the workload clusters and scalability considerations.
The deployment described in this document makes use of the following CIDR.
|Network Type||Port Group Name||Gateway CIDR||DHCP Pool||NSX ALB IP Pool|
|NSX ALB Mgmt Network||
|TKG Management Network||
|TKG Mgmt VIP Network||
|TKG Cluster VIP Network||
|TKG Workload VIP Network||
||172.16.70.1/24||N/A||172.16.70.100 - 172.16.70.200|
|TKG Workload Segment||
To prepare the firewall, you need to gather the following information:
|TKG management and workload networks||DNS Server
|TKG management and workload Networks||DHCP Server||UDP: 67, 68||Allows hosts to get DHCP addresses|
|TKG management and workload Networks||vCenter IP||TCP:443||Allows components to access vCenter to create VMs and storage volumes|
|TKG management, shared service, and workload cluster CIDR||Harbor Registry||TCP:443||
Allows components to retrieve container images.
This registry can be a local or a public image registry (projects.registry.vmware.com)
|TKG management cluster network||TKG cluster VIP network||TCP:6443||For management cluster to configure shared service and workload cluster.|
|TKG shared service cluster network
(Required only if using a separate network for shared service cluster)
|TKG cluster VIP network||TCP:6443||Allow shared cluster to register with management cluster|
|TKG workload cluster network||TKG cluster VIP network||TCP:6443||Allow workload cluster to register with management cluster|
|TKG management, shared service, and workload Networks||Avi Controllers (NSX ALB Management Network)||TCP:443||Allow Avi Kubernetes Operator (AKO) and AKO Operator (AKOO) access to Avi Controller|
|Avi Controllers (NSX ALB Management Network)||vCenter and ESXi Hosts||TCP:443||Allow Avi to discover vCenter objects and deploy SEs as required|
|Admin network||Bootstrap VM||SSH:22||To deploy, manage and configure TKG clusters|
Tanzu Kubernetes Grid management cluster is the first component that you deploy to get started with Tanzu Kubernetes Grid.
You can deploy the management cluster in two ways:
The Tanzu Kubernetes Grid Installation user interface shows that, in the current version, it is possible to install Tanzu Kubernetes Grid on vSphere (including VMware Cloud on AWS), AWS EC2, and Microsoft Azure. The UI provides a guided experience tailored to the IaaS, in this case, VMware vSphere.
The installation of Tanzu Kubernetes Grid on vSphere is done through the same installer UI but tailored to a vSphere environment.
This installation process will take you through the setup of a management cluster on your vSphere environment. Once the management cluster is deployed, you can make use of Tanzu Mission Control or Tanzu CLI to deploy Tanzu Kubernetes shared service and workload clusters.
The following table provides the recommendations for configuring NSX Advanced Load Balancer in a vSphere with Tanzu environment.
|Decision ID||Design Decision||Design Justification||Design Implications|
|TKO-ALB-001||Deploy NSX ALB controller cluster nodes on a network dedicated to NSX-ALB.||Isolate NSX ALB traffic from infrastructure management traffic and Kubernetes workloads.||Using the same network for NSX ALB Controller Cluster nodes allows for configuring a floating cluster IP address that will be assigned to the cluster leader.|
|TKO-ALB-002||Deploy 3 NSX ALB controllers nodes.||To achieve high availability for the NSX ALB platform.||In clustered mode, NSX ALB availability is not impacted by an individual controller node failure. The failed node can be removed from the cluster and redeployed if recovery is not possible.|
|TKO-ALB-003||Use static IP addresses for the NSX ALB controllers if DHCP cannot guarantee a permanent lease.||NSX ALB Controller cluster uses management IP addresses to form and maintain quorum for the control plane cluster. Any changes to management IP addresses will be disruptive.||NSX ALB Controller control plane might go down if the management IP addresses of the controller node change.|
|TKO-ALB-004||Use NSX ALB IPAM for service engine data network and virtual services.||Guarantees IP address assignment for service engine data NICs and virtual services.||Removes the corner case scenario when the DHCP server runs out of the lease or is down.|
|TKO-ALB-005||Reserve an IP address in the NSX ALB management subnet to be used as the cluster IP address for the controller cluster.||NSX ALB portal is always accessible over cluster IP address regardless of a specific individual controller node failure.||NSX ALB administration is not affected by an individual controller node failure.|
|TKO-ALB-006||Use separate VIP networks for application load balancing and L7 services in TKG clusters||Separate dev/test and prod workloads L7 load balancer traffic from each other.||Install AKO in TKG clusters manually using helm charts. Reference the VIP network to use in the AKO configuration.|
|TKO-ALB-007||Create separate service engine groups for TKG management and workload clusters.||This allows isolating load balancing traffic of the management and shared services cluster from workload clusters.||Create dedicated service engine groups under the vCenter cloud configured manually.|
|TKO-ALB-008||Shared service engines for the same type of workload (dev/test/prod) clusters.||Minimize the licensing cost.||
Each service engine contributes to the CPU core capacity associated with a license.
Sharing service engines can help reduce the licensing cost.
The key network recommendations for a production-grade Tanzu Kubernetes Grid deployment with NSX-T Data Center Networking are as follows:
|Decision ID||Design Decision||Design Justification||Design Implications|
|TKO-NET-001||Use separate networks for management cluster and workload clusters.||To have a flexible firewall and security policies.||Sharing the same network for multiple clusters can complicate firewall rules creation.|
|TKO-NET-002||Use separate networks for workload clusters based on their usage.||Isolate production Kubernetes clusters from dev/test clusters.||
A separate set of service engines can be used for separating dev/test workload clusters from prod clusters.
|TKO-NET-003||Configure DHCP for each TKG Cluster Network.||Tanzu Kubernetes Grid does not support static IP address assignments for Kubernetes VM components.||IP address pool can be used for the TKG clusters in absence of DHCP.|
|Decision ID||Design Decision||Design Justification||Design Implications|
|TKO-TKG-001||Deploy TKG management cluster from TKG Installer UI.||Simplified method of installation.||
When you deploy a management cluster by using the installer interface, it populates a cluster configuration file for the management cluster with the required parameters.
You can use the configuration file as a model for future deployments from the CLI.
|TKO-TKG-002||Register the management cluster with Tanzu Mission Control.||Tanzu Mission Control automates the creation of the Tanzu Kubernetes clusters and manages the life cycle of all clusters centrally.||Tanzu Mission Control also automates the deployment of Tanzu Packages in all Tanzu Kubernetes clusters associated with TMC.|
|TKO-TKG-003||Use NSX Advanced Load Balancer as your control plane endpoint provider and for application load balancing.||Eliminates the requirement for an external load balancer and additional configuration changes on your Tanzu Kubernetes Grid clusters.||NSX ALB is a true SDN solution and it offers a flexible deployment model and an automated way of scaling load balancer objects when needed.|
|TKO-TKG-004||Deploy Tanzu Kubernetes clusters in large form factor.||Allow TKG clusters integration with Tanzu SaaS components (Tanzu Mission Control, Tanzu Observability, and Tanzu Service Mesh).||
When TKG is integrated with SaaS endpoints, new pods or services are created in the target cluster and the pods have specific CPU requirements which can’t be fulfilled with medium and small-sized control plane or worker nodes.
|TKO-TKG-005||Deploy Tanzu Kubernetes clusters with prod plan.||This deploys multiple control plane nodes and provides high availability for the control plane.||TKG infrastructure is not impacted by single node failure.|
|TKO-TKG-006||Enable identity management for Tanzu Kubernetes Grid clusters.||To avoid usage of administrator credentials and ensure that required users with right roles have access to Tanzu Kubernetes Grid clusters.||
Pinniped package helps with integrating TKG Management cluster with LDAPS/OIDC authentication.
Workload cluster inherits the authentication configuration from the management cluster.
|TKO-TKG-007||Enable Machine Health Checks for TKG clusters.||vSphere HA and Machine Health Checks interoperably work together to enhance workload resiliency.||A MachineHealthCheck is a resource within the Cluster API which allows users to define conditions under which machines within a cluster are considered unhealthy. Remediation actions can be taken when MachineHealthCheck has identified a node as unhealthy.|
|TKO-TKG-008||Use Photon based image for TKG clusters.||TMC supports only Photon based images for deploying TKG clusters.||Provisioning clusters from TMC with Ubuntu or any custom images is still in development.|
The default installation of Tanzu Kubernetes Grid does not have any ingress controller installed. Users can use Contour (available for installation through Tanzu Packages) or any third-party ingress controller of their choice.
Contour is an open-source controller for Kubernetes ingress routing. Contour can be installed in the shared services cluster on any Tanzu Kubernetes Cluster. Deploying Contour is a prerequisite if you want to deploy the Prometheus, Grafana, and Harbor Packages on a workload cluster.
Another option is to use the NSX Advanced Load Balancer Kubernetes ingress controller which offers an advanced L7 ingress for containerized applications that are deployed in the Tanzu Kubernetes workload cluster.
For more information about the NSX Advanced Load Balancer ingress controller, see Configuring L7 Ingress with NSX Advanced Load Balancer.
The following table provides general recommendations on when you should use a specific ingress controller for your Kubernetes environment.
|Ingress Controller||Use Cases|
Use Contour when only north-south traffic is needed in a Kubernetes cluster. You can apply security policies for the north-south traffic by defining the policies in the application’s manifest file.
It’s a reliable solution for simple Kubernetes workloads.
|Istio||Use Istio ingress controller when you intend to provide security, traffic direction, and insights within the cluster (east-west traffic) and between the cluster and the outside world (north-south traffic).|
|NSX ALB ingress controller||
Use NSX ALB ingress controller when a containerized application requires features like local and global server load balancing (GSLB), web application firewall (WAF), performance monitoring, direct routing from LB to pod, etc.
Regardless of NSX Advanced Load Balancer Controller configuration, each controller cluster can achieve up to 5000 virtual services, which is a hard limit. For further details, refer to Sizing Compute and Storage Resources for NSX Advanced Load Balancer Controller(s).
|Controller Size||VM Configuration||Virtual Services||Avi SE Scale|
|Small||4 vCPUS, 12 GB RAM||0-50||0-10|
|Medium||8 vCPUS, 24 GB RAM||0-200||0-100|
|Large||16 vCPUS, 32 GB RAM||200-1000||100-200|
|Extra Large||24 vCPUS, 48 GB RAM||1000-5000||200-400|
For guidance on sizing your service engines (SEs), see Sizing Compute and Storage Resources for NSX Advanced Load Balancer Service Engine(s).
|Performance metric||1 vCPU core|
|SSL Throughput||1 Gb/s|
|SSL TPS (RSA2K)||~600|
|SSL TPS (ECC)||2500|
Multiple performance vectors or features may have an impact on performance. For instance, to achieve 1 Gb/s of SSL throughput and 2000 TPS of SSL with EC certificates, NSX Advanced Load Balancer recommends two cores.
NSX Advanced Load Balancer SEs may be configured with as little as 1 vCPU core and 1 GB RAM, or up to 36 vCPU cores and 128 GB RAM. SEs can be deployed in Active/Active or Active/Standby mode depending on the license tier used. NSX Advanced Load Balancer Essentials license doesn’t support Active/Active HA mode for SE.
|Decision ID||Design Decision||Design Justification||Design Implications|
|TKO-ALB-SE-001||Configure the high availability mode for SEs.||To mitigate a single point of failure for the NSX ALB data plane.||High availability for SEs is configured by setting the Elastic HA mode to Active/Active or N+M in the Service Engine Group.|
VMware Tanzu for Kubernetes Operations using Tanzu Kubernetes Grid includes Harbor as a container registry. Harbor provides a location for pushing, pulling, storing, and scanning container images used in your Kubernetes clusters.
Harbor registry is used for day-2 operations of the Tanzu Kubernetes workload clusters. Typical day-2 operations include tasks such as pulling images from Harbor for application deployment, pushing custom images to Harbor, etc.
You may use one of the following methods to install Harbor:
docker-compose- VMware recommends using this installation method in cases where Tanzu Kubernetes Grid is being installed in an air-gapped or Internet-less environment and no pre-existing image registry exists to host the Tanzu Kubernetes Grid system images. VM-based deployments are only supported by VMware Global Support Services to host the system images for air-gapped or Internet-less deployments. Do not use this method for hosting application images.
If you are deploying Harbor without a publicly signed certificate, you must include the Harbor root CA in your Tanzu Kubernetes Grid clusters. To do so, follow the procedure in Trust Custom CA Certificates on Cluster Nodes.
Tanzu Kubernetes Grid provides cluster monitoring services by implementing the open source Prometheus and Grafana projects.
Tanzu Kubernetes Grid includes signed binaries for Prometheus and Grafana that you can deploy on Tanzu Kubernetes clusters to monitor cluster health and services.
You deploy Prometheus and Grafana on Tanzu Kubernetes clusters. The following diagram shows how the monitoring components on a cluster interact.
Fluent Bit is a lightweight log processor and forwarder that allows you to collect data and logs from different sources, unify them, and send them to multiple destinations. Tanzu Kubernetes Grid includes signed binaries for Fluent Bit that you can deploy on management clusters and on Tanzu Kubernetes clusters to provide a log-forwarding service.
Tanzu for Kubernetes Operations includes Fluent Bit as a user managed package for integration with logging platforms such as vRealize LogInsight, Elasticsearch, Splunk, or other logging solutions. For information about configuring Fluent Bit to your logging provider, see Implement Log Forwarding with Fluent Bit.
You can deploy Fluent Bit on any management cluster or Tanzu Kubernetes clusters from which you want to collect logs. First, you configure an output plugin on the cluster from which you want to gather logs, depending on the endpoint that you use. Then, you deploy Fluent Bit on the cluster as a package.
vRealize Log Insight (vRLI) provides real-time log management and log analysis with machine learning based intelligent grouping, high-performance searching, and troubleshooting across physical, virtual, and cloud environments. vRLI already has a deep integration with the vSphere platform where you can get key actionable insights, and it can be extended to include the cloud native stack as well.
vRealize Log Insight appliance is available as a separate on-prem deployable product. You can also choose to go with the SaaS version vRealize Log Insight Cloud.
The Tanzu CLI creates the individual nodes of management clusters and Tanzu Kubernetes clusters according to the settings that you provide in the configuration file.
On vSphere, you can configure all node VMs to have the same predefined configurations, set different predefined configurations for control plane and worker nodes, or customize the configurations of the nodes. By using these settings, you can create clusters that have nodes with different configurations to the management cluster nodes. You can also create clusters in which the control plane nodes and worker nodes have different configurations.
Use Predefined Node Configurations
The Tanzu CLI provides the following predefined configurations for cluster nodes:
|Size||CPU||Memory (in GB)||Disk (in GB)|
To create a cluster in which all of the control plane and worker node VMs are the same size, specify the
SIZE variable. If you set the
SIZE variable, all nodes will be created with the configuration that you set.
To create a cluster in which the control plane and worker node VMs are different sizes, specify the
You can combine the
WORKER_SIZE options with the
SIZE option. For example, if you specify
SIZE: "large" with
WORKER_SIZE: "extra-large", the control plane nodes will be set to large and worker nodes will be set to extra-large.
Define Custom Node Configurations
You can customize the configuration of the nodes rather than using the predefined configurations.
To use the same custom configuration for all nodes, specify the
To define different custom configurations for control plane nodes and worker nodes, specify the
Tanzu Kubernetes Grid on vSphere on hyper-converged hardware offers high-performance potential, convenience, and addresses the challenges of creating, testing, and updating on-premises Kubernetes platforms in a consolidated production environment. This validated approach will result in a near-production quality installation with all the application services needed to serve combined or uniquely separated workload types through a combined infrastructure solution.
This plan meets many Day 0 needs for quickly aligning product capabilities to full stack infrastructure, including networking, firewalling, load balancing, workload compute alignment, and other capabilities.
For instructions on how to deploy this reference design, see Deploy Tanzu for Kubernetes Operations on vSphere with VMware VDS.