Skip to content

Commit 9254486

Browse files
Update README.md
1 parent 6e4a90e commit 9254486

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

  • samples/features/sql-big-data-cluster/deployment/aks

samples/features/sql-big-data-cluster/deployment/aks/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ python deploy-sql-big-data-aks.py
4242
4343
When prompted, provide your input for Azure subscription ID, Azure resource group to create the resources in, and Docker credentials. Optionally, you can also provide your input for below configurations or use the defaults provided:
4444
- azure_region
45-
- vm_size - we recommend to use a VM size to accommodate your workload. For an optimal experience while you are validating basic scenarios, we recommend at least 8 vCPUs and 32GB memory across all agent nodes in the cluster. The script uses **Standard_L8s** as default.
45+
- vm_size - we recommend to use a VM size to accommodate your workload. For an optimal experience while you are validating basic scenarios, we recommend at least 8 vCPUs and 64GB memory across all agent nodes in the cluster. The script uses **Standard_L8s** as default. A default size configuration also uses about 24 disks for persistent volume claims across all components.
4646
- aks_node_count - this is the number of the worker nodes for the AKS cluster, excluding master node. The script is using a default of 1 agent node. This is the minimum required for this VM size to have enough resources and disks to provision all the necessary persistent volumes.
4747
- cluster_name - this value is used for both AKS cluster and SQL big data cluster created on top of AKS. Note that the name of the SQL big data cluster is going to be a Kubernetes namespace
4848
- password - same value is going to be used for all accounts that require user password input: SQL Server master instance SA account, controller user and Knox user

0 commit comments

Comments
 (0)