-
Notifications
You must be signed in to change notification settings - Fork 68
/
_resource-config.html.md.erb
33 lines (33 loc) · 2.51 KB
/
_resource-config.html.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
For each job, review the **Automatic** values in the following fields:
* **INSTANCES**: Tanzu Kubernetes Grid Integrated Edition defaults to the minimum configuration.
If you want a highly available configuration (beta), scale the number of VM instances as follows:
1. To configure your Tanzu Kubernetes Grid Integrated Edition database for high availability (beta),
increase the **INSTANCES** value for **TKGI Database** to `3`.
1. To configure your Tanzu Kubernetes Grid Integrated Edition API and UAA for high availability (beta),
increase the **INSTANCES** value for **TKGI API** to `2` or more.
<p class="note warning"><strong>Warning:</strong> High availability mode is a beta feature. Do not scale your <strong>TKGI API</strong> or <strong>TKGI Database</strong> to more than one instance in production environments.</p>
<% if current_page.data.iaas == "Azure" %>
<p class="note"><strong>Note</strong>: On Azure, you must reconfigure your
TKGI API load balancer backend pool
whenever you modify your TKGI API VM group.
For more information about configuring your TKGI API
load balancer backend pool, see
<a href="azure-api-load-balancer.html#create-load-balancer">Create a Load Balancer</a>
in <i>Configuring an Azure Load Balancer for the TKGI API</i>.
</p>
<% end %>
<% if current_page.data.iaas == "vSphere-NSX-T" %>
<p class="note"><strong>Note</strong>: On vSphere with NSX, you must manually deploy
an NSX load balancer so that you can select it as part of the resource configuration.
For more information, see
<a href="nsxt-lb-tkgi-api.html">Provisioning an NSX Load Balancer for the TKGI API Server</a>.
</p>
<% end %>
* **VM TYPE**: By default, the **TKGI Database** and **TKGI API** jobs are set to the same **Automatic** VM type.
If you want to adjust this value, we recommend that you select the same VM type for both jobs.
<p class="note"><strong>Note:</strong> The <strong>Automatic</strong> <strong>VM TYPE</strong> values match the recommended resource configuration for the <strong>TKGI API</strong>
and <strong>TKGI Database</strong> jobs.
</p>
* **PERSISTENT DISK TYPE**: By default, the **TKGI Database** and **TKGI API** jobs are set to the same persistent disk type.
If you want to adjust this value, you can change the persistent disk type for each of the jobs independently.
Using the same persistent disk type for both jobs is not required.