You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/CONFIG-VARS.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,7 +63,7 @@ To do set these permissions as part of this Terraform script, specify ranges of
63
63
64
64
NOTE: When deploying infrastructure into a private network (e.g. a VPN), with no public endpoints, the options documented in this block are not applicable.
65
65
66
-
NOTE: The script will either create a new NSG, or use an existing NSG, if specified in the [`nsg_name`](#use-existing) variable.
66
+
NOTE: The script will either create a new NSG, or use an existing NSG, if specified in the [`nsg_name`](#use-existing) variable.
67
67
68
68
You can use `default_public_access_cidrs` to set a default range for all created resources. To set different ranges for other resources, define the appropriate variable. Use an empty list `[]` to disallow access explicitly.
69
69
@@ -75,7 +75,7 @@ You can use `default_public_access_cidrs` to set a default range for all created
75
75
| postgres_public_access_cidrs | IP address ranges allowed to access the Azure PostgreSQL Flexible Server | list of strings || Opens port 5432 by adding Ingress Rule on the NSG. Only used when creating postgres instances. |
76
76
| acr_public_access_cidrs | IP address ranges allowed to access the ACR instance | list of strings || Only used with `create_container_registry=true`|
77
77
78
-
**NOTE:** In a SCIM environment, the AzureActiveDirectory service tag must be granted access to port 443/HTTPS for the Ingress IP address.
78
+
**NOTE:** In a SCIM environment, the AzureActiveDirectory service tag must be granted access to port 443/HTTPS for the Ingress IP address.
79
79
80
80
## Networking
81
81
@@ -147,7 +147,7 @@ Example for the `subnet_names` variable:
147
147
```yaml
148
148
subnet_names = {
149
149
## Required subnets
150
-
'aks': '<my_aks_subnet_name>',
150
+
'aks': '<my_aks_subnet_name>',
151
151
'misc': '<my_misc_subnet_name>',
152
152
153
153
## If using ha storage then the following is also required
@@ -261,7 +261,7 @@ In addition, you can control the placement for the additional node pools using t
261
261
262
262
| Name | Description | Type | Default | Notes |
263
263
| :--- | ---: | ---: | ---: | ---: |
264
-
| node_pools_availability_zone | Availability Zone for the additional node pools and the NFS VM, for `storage_type="standard"'| string | "1" | The possible values depend on the region set in the "location" variable. |
264
+
| node_pools_availability_zone | Availability Zone for the additional node pools and the NFS VM, for `storage_type="standard"`| string | "1" | The possible values depend on the region set in the "location" variable. |
265
265
| node_pools_proximity_placement | Co-locates all node pool VMs for improved application performance. | bool | false | Selecting proximity placement imposes an additional constraint on VM creation and can lead to more frequent denials of VM allocation requests. We recommend that you set `node_pools_availability_zone=""` and allocate all required resources at one time by setting `min_nodes` and `max_nodes` to the same value for all node pools. Additional information: [Proximity Group Placement](./user/ProximityPlacementGroup.md). |
description="Specifies a list of Availability Zones in which the Kubernetes Cluster Node Pool should be located. Changing this forces a new Kubernetes Cluster Node Pool to be created."
378
+
type=list(string)
379
+
default=null
380
+
}
381
+
376
382
variable"node_pools_proximity_placement" {
377
383
type=bool
378
384
default=false
@@ -560,8 +566,8 @@ variable "subnet_names" {
560
566
description="Map subnet usage roles to existing subnet names"
0 commit comments