-
Notifications
You must be signed in to change notification settings - Fork 0
/
variables.tf
260 lines (247 loc) · 10.9 KB
/
variables.tf
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
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
variable "resource_group_name" {
type = string
description = "Name of resource group where cluster will be deployed"
}
variable "resource_group_id" {
type = string
description = "ID of resource group where cluster will be deployed"
}
variable "location" {
type = string
description = "Azure region where cluster will be deployed"
}
variable "manifest" {
description = <<DESCRIPTION
**Manifest definition**
Provide cluster configuration. Here is example with documentation in YAML form.
Suggested approach is to have separate folders for each cluster from which you reference this module and store manifest in YAML file. Call this module and pass its values using yamldecode(file("manifest.yaml"))
```yaml
## -- Definition of enterprise container platform cluster
## This file is used as input to Terraform, Helm/Argo and other tools
## providing single place to define cluster configuration.
# Name of cluster
cluster_name: cluster01
# Cluster Kubernetes version, use short style (eg. 1.24) especially if auto-upgrade is enabled
# You can also disable auto-upgrade and use explicit long version (eg. 1.24.5)
cluster_version: 1.24
# Cluster SKU, use Free for development and Standard for production
cluster_sku: Free
# Cluster auto-upgrade channel: patch, stable, rapid, node-image or none
cluster_upgrade_channel: patch
# OS auto-upgrade channel: SecurityPatch, NodeImage, Unmanaged or None -- PLACEHOLDER, wait for azurerm to implement this preview feature
os_upgrade_channel: SecurityPatch
# Cluster region
location: northeurope
# Cluster resource group
resource_group_name: cluster01
# Cluster subscription id
subscription_id: d3b7888f-c26e-4961-a976-ff9d5b31dfd3
# Cluster tenant id
tenant_id: d6af5f85-2a50-4370-b4b5-9b9a55bcb0dc
# Resource ID of network subnet for API server (must be delegated)
api_subnet_id: /subscriptions/d3b7888f-c26e-4961-a976-ff9d5b31dfd3/resourceGroups/demo-infra/providers/Microsoft.Network/virtualNetworks/cluster01/subnets/aks-api
# Resource ID of private cluster DNS Zone
cluster_private_dns_zone_id: /subscriptions/d3b7888f-c26e-4961-a976-ff9d5b31dfd3/resourceGroups/demo-infra/providers/Microsoft.Network/privateDnsZones/privatelink.northeurope.azmk8s.io
# Resource ID of private endpoint KeyVault DNS zone
keyvault_private_dns_zone_id: /subscriptions/d3b7888f-c26e-4961-a976-ff9d5b31dfd3/resourceGroups/demo-infra/providers/Microsoft.Network/privateDnsZones/privatelink.vaultcore.azure.net
# Definition of ingress types, versions and subnets
ingress_types:
# One or more NGINX ingresses with their subnets (can share the same if needed)
nginx:
nginx-ingress-internal:
version: 4.5.2
subnet_id: /subscriptions/d3b7888f-c26e-4961-a976-ff9d5b31dfd3/resourceGroups/demo-infra/providers/Microsoft.Network/virtualNetworks/cluster01/subnets/aks-inbound-internal
subnet_name: aks-inbound-internal
nginx-ingress-external:
version: 4.5.2
subnet_id: /subscriptions/d3b7888f-c26e-4961-a976-ff9d5b31dfd3/resourceGroups/demo-infra/providers/Microsoft.Network/virtualNetworks/cluster01/subnets/aks-inbound-external
subnet_name: aks-inbound-external
# One or more Azure API Management self-hosted gateways with their subnets (can share the same if needed)
apim:
apim-internal:
api_management_id: /subscriptions/d3b7888f-c26e-4961-a976-ff9d5b31dfd3/resourceGroups/demo-infra/providers/Microsoft.ApiManagement/service/hclhrwrfduhg
api_management_configuration_endpoint: hclhrwrfduhg.configuration.azure-api.net
subnet_id: /subscriptions/d3b7888f-c26e-4961-a976-ff9d5b31dfd3/resourceGroups/demo-infra/providers/Microsoft.Network/virtualNetworks/cluster01/subnets/aks-inbound-internal
subnet_name: aks-inbound-internal
# System node pool configuration
system_nodepool:
# VM SKU
node_sku: Standard_D2as_v4
# Preferably start with 3 nodes
node_count: 3
# Should not have less than 2 for HA, preferably 3
min_count: 3
# Use more than min if there are custom platform components that autoscale
max_count: 6
# Resource ID of network subnet for system nodes
subnet_id: /subscriptions/d3b7888f-c26e-4961-a976-ff9d5b31dfd3/resourceGroups/demo-infra/providers/Microsoft.Network/virtualNetworks/cluster01/subnets/aks-system
# User node pool configurations for shared nodes, define at least one
shared_nodepools:
# Name of nodepool, for example standard VM size
standard:
# VM SKU
node_sku: Standard_D4as_v4
# Starting number of nodes, usualy not 0
node_count: 0
# Use 0 if you expect empty cluster is possible (batch workloads)
min_count: 0
# Maximum autoscaled nodes in nodepool
max_count: 2
# Resource ID of network subnet for this nodepool
subnet_id: /subscriptions/d3b7888f-c26e-4961-a976-ff9d5b31dfd3/resourceGroups/demo-infra/providers/Microsoft.Network/virtualNetworks/cluster01/subnets/aks-shared
# Additional nodepools to provide differentiated SKUs, eg. high memory configuration
highmem:
# VM SKU
node_sku: Standard_E4as_v4
# You might start with 0 nodes if you expect previous nodepool to be enough most of the time
node_count: 0
# Use 0 for scale-to-zero
min_count: 0
# Maximum autoscaled nodes in nodepool
max_count: 2
# Resource ID of network subnet for this nodepool
subnet_id: /subscriptions/d3b7888f-c26e-4961-a976-ff9d5b31dfd3/resourceGroups/demo-infra/providers/Microsoft.Network/virtualNetworks/cluster01/subnets/aks-shared
# Definitions of applications in classes 1-3 that will leverage shared nodepools
standard_applications:
# Application inventory ID
sas101:
# Map of users with read access to resources of this application
permanent_readers:
# Friendly name (used for clarity)
aks-u1:
# Object ID of this user as per AAD (this is also called principal ID)
object_id: 39bb675c-f6a2-48c9-b809-9fb8825ec30e
# PLACEHOLDER - indicates use can be promoted to writers using AAD PIM (need to be AAD Group based solution)
eligible_for_write_elevation: true
aks-u2:
object_id: c136f236-5ca2-4f28-bf14-00f55f383c85
eligible_for_write_elevation: false
# Map of users with write access to resources of this application
permanent_writers:
aks-u3:
object_id: c153cfa5-82b3-409e-a95f-45741a070362
aks-u4:
object_id: ab83def6-3f08-42b0-90c2-0332ee48fca3
# Allowed one or more ingress_types defined above - this causes network policy to filter traffic accordingly
ingress_types:
- nginx-ingress-internal
- apim-internal
# OPTIONALLY provide list of security policy exclusions
policy_exclusions:
# You can override allowed image regex list which will replace default one - can be more or less restrictive depending on application needs
allowed_images_override:
- "docker.io/.+"
- "mcr.microsoft.com/.+"
# Name of policy as per policies.tf file
no_priv_containers:
# Set this to true to disable this policy for this application. Set to false or do not include here if policy should stay active
exclude_whole_namespace: false
# Where possible you can make exceptions on per-image basis (see policy.tf for details what policies support this)
image_exclusions:
- docker.io/registry1/image1*
- docker.io/registry2/*
# Example of another policy
https_ingress_only:
exclude_whole_namespace: true
limit_volumes:
exclude_whole_namespace: false
image_exclusions:
- docker.io/registry1/image1*
- docker.io/registry2/*
no_priv_escalation:
exclude_whole_namespace: true
no_sysctl:
exclude_whole_namespace: true
no_sysadmin_cap:
exclude_whole_namespace: false
image_exclusions:
- docker.io/registry1/image1*
- docker.io/registry2/*
no_external_lb:
exclude_whole_namespace: true
no_api_credentials:
exclude_whole_namespace: false
image_exclusions:
- docker.io/registry1/image1*
- docker.io/registry2/*
sas102:
permanent_readers:
aks-u1:
object_id: 39bb675c-f6a2-48c9-b809-9fb8825ec30e
eligible_for_write_elevation: false
permanent_writers:
aks-u4:
object_id: ab83def6-3f08-42b0-90c2-0332ee48fca3
eligible_writers: {}
ingress_types:
- nginx-ingress-internal
policy_exclusions:
allowed_images_override:
- "mcr.microsoft.com/.+"
no_priv_containers:
exclude_whole_namespace: true
image_exclusions:
- docker.io/registry1/image1*
- docker.io/registry2/*
limit_volumes:
exclude_whole_namespace: true
no_priv_escalation:
exclude_whole_namespace: false
image_exclusions:
- docker.io/registry2/*
no_root_containers:
exclude_whole_namespace: false
image_exclusions:
- docker.io/registry2/*
something:
exclude_whole_namespace: true
sas103:
permanent_readers:
aks-u4:
object_id: ab83def6-3f08-42b0-90c2-0332ee48fca3
eligible_for_write_elevation: true
permanent_writers:
aks-u3:
object_id: c153cfa5-82b3-409e-a95f-45741a070362
ingress_types:
- nginx-ingress-external
# Definitions of class 4 applications that will have dedicated nodepool
confidential_applications:
# Application inventory ID
sas201:
# VM SKU
node_sku: Standard_D2as_v4
# Initial node count, setting this to 0 will lead to 5 minute delay before first pod is scheduled when team deploy something
node_count: 1
# Use 0 if you expect empty cluster is possible (batch workloads)
min_count: 1
# Maximum autoscaled nodes in nodepool, can be used to cap costs, but preferably keep it higher than minimum
max_count: 1
# Map of users with read access to resources of this application
permanent_readers:
# Friendly name (used for clarity)
aks-u1:
# Object ID of this user as per AAD (this is also called principal ID)
object_id: 39bb675c-f6a2-48c9-b809-9fb8825ec30e
# PLACEHOLDER - indicates use can be promoted to writers using AAD PIM (need to be AAD Group based solution)
eligible_for_write_elevation: false
# Map of users with write access to resources of this application
permanent_writers:
aks-u4:
object_id: ab83def6-3f08-42b0-90c2-0332ee48fca3
# Allowed one or more ingress_types defined above - this causes network policy to filter traffic accordingly
ingress_types:
- nginx-ingress-internal
- apim-internal
# OPTIONALLY provide list of security policy exclusions
policy_exclusions:
no_priv_containers:
exclude_whole_namespace: false
image_exclusions:
- docker.io/registry1/image1*
- docker.io/registry2/*
# Resource ID of network subnet for dedicated nodepool
subnet_id: /subscriptions/d3b7888f-c26e-4961-a976-ff9d5b31dfd3/resourceGroups/demo-infra/providers/Microsoft.Network/virtualNetworks/cluster01/subnets/s201
```
DESCRIPTION
}