Project: YugabyteDB (App Definition and Development / Database)
File: vmware-tanzu.md

title: Configure the VMware Tanzu cloud provider headerTitle: Create provider configuration linkTitle: Create provider configuration description: Configure the VMware Tanzu provider configuration headContent: Configure a VMWare Tanzu provider configuration menu: v2.18_yugabyte-platform: identifier: set-up-cloud-provider-4-vmware-tanzu parent: configure-yugabyte-platform weight: 20 type: docs <ul class="nav nav-tabs-alt nav-tabs-yb"> <li> <a href="../aws/" class="nav-link"> <i class="fa-brands fa-aws"></i> AWS </a> </li> <li> <a href="../gcp/" class="nav-link"> <i class="fa-brands fa-google" aria-hidden="true"></i> GCP </a> </li> <li> <a href="../azure/" class="nav-link"> <i class="icon-azure" aria-hidden="true"></i> Azure </a> </li> <li> <a href="../kubernetes/" class="nav-link"> <i class="fa-regular fa-dharmachakra" aria-hidden="true"></i> Kubernetes </a> </li> <li> <a href="../vmware-tanzu/" class="nav-link active"> <i class="fa-solid fa-cubes" aria-hidden="true"></i> VMware Tanzu </a> </li> <li> <a href="../openshift/" class="nav-link"> <i class="fa-brands fa-redhat" aria-hidden="true"></i> OpenShift </a> </li> <li> <a href="../on-premises/" class="nav-link"> <i class="fa-solid fa-building"></i> On-premises </a> </li> </ul> Before you can deploy universes using YugabyteDB Anywhere, you must create a provider configuration. A provider configuration describes your cloud environment (its service account, regions and availability zones, NTP server, the certificates that will be used to SSH to VMs, the Linux disk image to be used for configuring the nodes, and so on). The provider configuration is used as an input when deploying a universe, and can be reused for many universes. Before you start, ensure that you have created the so YugabyteDB Anywhere can use the provided credentials to automatically provision and deprovision Kubernetes pods that run the YugabyteDB universe. To configure any TKG edition (that is, either TKG-Integrated, TKG-Service, or TKG-Multicloud), navigate to Configs > Infrastructure > VMware Tanzu. This lists all currently configured VMWare Tanzu providers. To create a TKG provider, click Create Kubernetes Config. For more information, refer to . Set the Kubernetes Provider Type to VMWare Tanzu. For information on the Kubernetes Provider settings, refer to . To add service-level annotations, use the following : ```config serviceEndpoints: name: "yb-master-service" type: "LoadBalancer" annotations: service.beta.kubernetes.io/aws-load-balancer-internal: "0.0.0.0/0" app: "yb-master" ports: ui: "7000" name: "yb-tserver-service" type: "LoadBalancer" annotations: service.beta.kubernetes.io/aws-load-balancer-internal: "0.0.0.0/0" app: "yb-tserver" ports: ycql-port: "9042" yedis-port: "6379" ysql-port: "5433" ``` To disable LoadBalancer, use the following overrides: ```configuration enableLoadBalancer: False ``` To change the cluster domain name, use the following overrides: ```configuration domainName: my.cluster ``` To add annotations at the StatefulSet level, use the following overrides: ```configuration networkAnnotation: annotation1: 'foo' annotation2: 'bar' ``` VMware Tanzu Application Service is no longer actively supported and the following information is considered legacy. If you choose to use VMware Tanzu Application Service, before creating the service instance, ensure that the following is available: The YugabyteDB tile is installed in your PCF marketplace. The cloud provider is configured in the YugabyteDB Anywhere instance in your PCF environment. You can create a YugabyteDB service instance via the App Manager UI or Cloud Foundry (cf) command-line interface

In your PCF App manager, navigate to the marketplace and select YugabyteDB. Read descriptions of the available service plans to identify the resource requirements and intended environment, as shown in the following illustration: Select the service plan. Complete the service instance configuration, as shown in the following illustration: You can view the marketplace and plan description in the cf CLI by executing the following command: ```sh cf marketplace -s yugabyte-db ``` The output should be similar to the following: ```output service plan description free or paid x-small Cores: 2, Memory (GB): 4 paid small Cores: 4, Memory (GB): 7 paid medium Cores: 8, Memory (GB): 15 paid large Cores: 16, Memory (GB): 15 paid x-large Cores: 32, Memory (GB): 30 paid ``` After you decide on the service plan, you can launch the YugabyteDB service instance by executing the following command: ```sh cf create-service yugabyte-db x-small yb-demo -c '{"universe_name": "yb-demo"}' ``` You can specify override options when you create a service instance using the YugabyteDB service broker. Depending on the cloud providers configured for your YugabyteDB Anywhere, you can create Yugabyte service instances by providing overrides. To provision in AWS or GCP cloud, your overrides should include the appropriate `providertype` and `regioncodes` as an array, as follows: ```configuration { "universe_name": "cloud-override-demo", "provider_type": "gcp", # gcp for Google Cloud, aws for Amazon Web Service "region_codes": ["us-west1"] # comma delimited list of regions } ``` To provision in Kubernetes, your overrides should include the appropriate `providertype` and `kubeprovider` type, as follows: ```configuration { "universe_name": "cloud-override-demo", "provider_type": "kubernetes", "kube_provider": "gke" # gke for Google Compute Engine, pks for Pivotal Container Service (default) } ``` To override the number of nodes, include the `num_nodes` with the desired value, and then include this parameter along with other parameters for the cloud provider, as follows: ```configuration { "universe_name": "cloud-override-demo", "num_nodes": 4 # default is 3 nodes. } ``` To override the replication factor, include `replication` with the desired value, and then include this parameter along with other parameters for the cloud provider, as follows: ```configuration { "universe_name": "cloud-override-demo", "replication": 5, "numnodes": 5 # if the replication factor is 5, numnodes must be 5 minimum } ``` replication must be set to 1, 3, 5, or 7. To override the volume settings, include `numvolumes` with the desired value, as well as `volumesize` with the volume size in GB for each of those volumes. For example, to have two volumes with 100GB each, overrides should be specified as follows: ```configuration { "universe_name": "cloud-override-demo", "num_volumes": 2, "volume_size": 100 } ``` To override the YugabyteDB software version to be used, include `yb_version` with the desired value, ensuring that this version exists in YugabyteDB Anywhere, as follows: ```configuration { "universe_name": "cloud-override-demo", "yb_version": "1.1.6.0-b4" } ```