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: README.md
+8-5
Original file line number
Diff line number
Diff line change
@@ -190,6 +190,7 @@ The following sections provide a full list of configuration in- and output varia
190
190
| enable\_worker\_groups\_launch\_template | Flag to enable Worker Group Launch Templates |`bool`|`false`| no |
191
191
| encrypt\_volume\_self | Encrypt the ebs and root volume for the self managed worker nodes. This is only valid for the worker group launch template |`bool`|`false`| no |
192
192
| force\_destroy | Flag to determine whether storage buckets get forcefully destroyed. If set to false, empty the bucket first in the aws s3 console, else terraform destroy will fail with BucketNotEmpty error |`bool`|`false`| no |
193
+
| force\_destroy\_subdomain | Flag to determine whether subdomain zone get forcefully destroyed. If set to false, empty the sub domain first in the aws Route 53 console, else terraform destroy will fail with HostedZoneNotEmpty error |`bool`|`false`| no |
193
194
| ignoreLoadBalancer | Flag to specify if jx boot will ignore loadbalancer DNS to resolve to an IP |`bool`|`false`| no |
194
195
| install\_kuberhealthy | Flag to specify if kuberhealthy operator should be installed |`bool`|`true`| no |
195
196
| iops | The IOPS value |`number`|`0`| no |
@@ -198,6 +199,7 @@ The following sections provide a full list of configuration in- and output varia
198
199
| jx\_bot\_username | Bot username used to interact with the Jenkins X cluster git repository |`string`|`""`| no |
199
200
| jx\_git\_url | URL for the Jenkins X cluster git repository |`string`|`""`| no |
200
201
| key\_name | The ssh key pair name |`string`|`""`| no |
202
+
| local-exec-interpreter | If provided, this is a list of interpreter arguments used to execute the command |`list(string)`| <pre>[<br> "/bin/bash",<br> "-c"<br>]</pre> | no |
201
203
| lt\_desired\_nodes\_per\_subnet | The number of worker nodes in each Subnet (AZ) if using Launch Templates |`number`|`1`| no |
202
204
| lt\_max\_nodes\_per\_subnet | The maximum number of worker nodes in each Subnet (AZ) if using Launch Templates |`number`|`2`| no |
203
205
| lt\_min\_nodes\_per\_subnet | The minimum number of worker nodes in each Subnet (AZ) if using Launch Templates |`number`|`1`| no |
@@ -211,10 +213,10 @@ The following sections provide a full list of configuration in- and output varia
| nginx\_namespace | Name of the nginx namespace |`string`|`"nginx"`| no |
213
215
| nginx\_release\_name | Name of the nginx release name |`string`|`"nginx-ingress"`| no |
214
-
| nginx\_values\_file | Name of the values file which holds the helm chart values |`string`|`"values.yaml"`| no |
216
+
| nginx\_values\_file | Name of the values file which holds the helm chart values |`string`|`"nginx_values.yaml"`| no |
215
217
| node\_group\_ami | ami type for the node group worker intances |`string`|`"AL2_x86_64"`| no |
216
218
| node\_group\_disk\_size | node group worker disk size |`string`|`"50"`| no |
217
-
| node\_groups\_managed | List of managed node groups to be created and their respective settings | <pre>map(object({<br> ami_type = string<br> disk_size = number<br> desired_capacity = number<br> max_capacity = number<br> min_capacity = number<br> instance_types = list(string)<br> launch_template_id = string<br> launch_template_version = string<br> k8s_labels = map(string)<br> }))</pre>|`{}`| no |
219
+
| node\_groups\_managed | List of managed node groups to be created and their respective settings |`any`|<pre>{<br> "eks-jx-node-group": {}<br>}</pre> | no |
218
220
| node\_machine\_type | The instance type to use for the cluster's worker nodes |`string`|`"m5.large"`| no |
219
221
| private\_subnets | The private subnet CIDR block to use in the created VPC |`list(string)`| <pre>[<br> "10.0.4.0/24",<br> "10.0.5.0/24",<br> "10.0.6.0/24"<br>]</pre> | no |
220
222
| production\_letsencrypt | Flag to use the production environment of letsencrypt in the `jx-requirements.yml` file |`bool`|`false`| no |
@@ -226,9 +228,9 @@ The following sections provide a full list of configuration in- and output varia
226
228
| spot\_price | The spot price ceiling for spot instances |`string`|`"0.1"`| no |
227
229
| subdomain | The subdomain to be added to the apex domain. If subdomain is set, it will be appended to the apex domain in `jx-requirements-eks.yml` file |`string`|`""`| no |
228
230
| subnets | The subnet ids to create EKS cluster in if create\_vpc is false |`list(string)`|`[]`| no |
231
+
| tls\_cert | TLS certificate encrypted with Base64 |`string`|`""`| no |
229
232
| tls\_email | The email to register the LetsEncrypt certificate with. Added to the `jx-requirements.yml` file |`string`|`""`| no |
230
-
| tls\_key | The customer's private key that he got from some CA. It could be as base64 encrypted content or path to file. |`string`|`""`| no |
231
-
| tls\_cert | The customer's certificate that he got from some CA. It could be as base64 encrypted content or path to file. |`string`|`""`| no |
233
+
| tls\_key | TLS key encrypted with Base64 |`string`|`""`| no |
232
234
| use\_asm | Flag to specify if AWS Secrets manager is being used |`bool`|`false`| no |
233
235
| use\_kms\_s3 | Flag to determine whether kms should be used for encrypting s3 buckets |`bool`|`false`| no |
234
236
| use\_vault | Flag to control vault resource creation |`bool`|`true`| no |
@@ -241,7 +243,7 @@ The following sections provide a full list of configuration in- and output varia
241
243
| volume\_size | The volume size in GB |`number`|`50`| no |
242
244
| volume\_type | The volume type to use. Can be standard, gp2 or io1 |`string`|`"gp2"`| no |
243
245
| vpc\_cidr\_block | The vpc CIDR block |`string`|`"10.0.0.0/16"`| no |
244
-
| vpc\_id | The VPC to create EKS cluster in if create\_vpc is false |`string`|`""`| no |
246
+
| vpc\_id | The VPC to create EKS cluster in if create\_vpc is false |`string`|`""`| no |
245
247
| vpc\_name | The name of the VPC to be created for the cluster |`string`|`"tf-vpc-eks"`| no |
246
248
247
249
#### Outputs
@@ -258,6 +260,7 @@ The following sections provide a full list of configuration in- and output varia
258
260
| cm\_cainjector\_iam\_role | The IAM Role that the CM CA Injector pod will assume to authenticate |
259
261
| connect | "The cluster connection string to use once Terraform apply finishes,<br>this command is already executed as part of the apply, you may have to provide the region and<br>profile as environment variables " |
260
262
| controllerbuild\_iam\_role | The IAM Role that the ControllerBuild pod will assume to authenticate |
263
+
| eks\_module | The output of the terraform-aws-modules/eks/aws module for use in terraform |
261
264
| external\_dns\_iam\_role | The IAM Role that the External DNS pod will assume to authenticate |
262
265
| jx\_requirements | The jx-requirements rendered output |
263
266
| lts\_logs\_bucket | The bucket where logs from builds will be stored |
0 commit comments