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
@@ -150,7 +150,6 @@ MIT Licensed. See [LICENSE](https://github.com/terraform-aws-modules/terraform-a
150
150
| kubernetes | >= 1.11.1 |
151
151
| local | >= 1.4 |
152
152
| null | >= 2.1 |
153
-
| random | >= 2.1 |
154
153
| template | >= 2.1 |
155
154
156
155
## Inputs
@@ -205,8 +204,7 @@ MIT Licensed. See [LICENSE](https://github.com/terraform-aws-modules/terraform-a
205
204
| worker\_create\_cluster\_primary\_security\_group\_rules | Whether to create security group rules to allow communication between pods on workers and pods using the primary cluster security group. |`bool`|`false`| no |
206
205
| worker\_create\_initial\_lifecycle\_hooks | Whether to create initial lifecycle hooks provided in worker groups. |`bool`|`false`| no |
207
206
| worker\_create\_security\_group | Whether to create a security group for the workers or attach the workers to `worker_security_group_id`. |`bool`|`true`| no |
208
-
| worker\_groups | A list of maps defining worker group configurations to be defined using AWS Launch Configurations. See workers\_group\_defaults for valid keys. |`any`|`[]`| no |
209
-
| worker\_groups\_launch\_template | A list of maps defining worker group configurations to be defined using AWS Launch Templates. See workers\_group\_defaults for valid keys. |`any`|`[]`| no |
207
+
| worker\_groups | A map of maps defining worker group configurations to be defined using AWS Launch Templates. See workers\_group\_defaults for valid keys. |`any`|`{}`| no |
210
208
| worker\_security\_group\_id | If provided, all workers will be attached to this security group. If not given, a security group will be created with necessary ingress/egress to work with the EKS cluster. |`string`|`""`| no |
211
209
| worker\_sg\_ingress\_from\_port | Minimum port number from which pods will accept communication. Must be changed to a lower value if some pods in your cluster will expose a port lower than 1025 (e.g. 22, 80, or 443). |`number`|`1025`| no |
212
210
| workers\_additional\_policies | Additional policies to be added to workers |`list(string)`|`[]`| no |
@@ -235,17 +233,7 @@ MIT Licensed. See [LICENSE](https://github.com/terraform-aws-modules/terraform-a
235
233
| node\_groups | Outputs from EKS node groups. Map of maps, keyed by var.node\_groups keys |
236
234
| oidc\_provider\_arn | The ARN of the OIDC Provider if `enable_irsa = true`. |
237
235
| security\_group\_rule\_cluster\_https\_worker\_ingress | Security group rule responsible for allowing pods to communicate with the EKS cluster API. |
238
-
| worker\_iam\_instance\_profile\_arns | default IAM instance profile ARN for EKS worker groups |
239
-
| worker\_iam\_instance\_profile\_names | default IAM instance profile name for EKS worker groups |
240
-
| worker\_iam\_role\_arn | default IAM role ARN for EKS worker groups |
241
-
| worker\_iam\_role\_name | default IAM role name for EKS worker groups |
236
+
| worker\_groups | Outputs from EKS worker groups. Map of maps, keyed by var.worker\_groups keys |
242
237
| worker\_security\_group\_id | Security group ID attached to the EKS workers. |
243
-
| workers\_asg\_arns | IDs of the autoscaling groups containing workers. |
244
-
| workers\_asg\_names | Names of the autoscaling groups containing workers. |
245
-
| workers\_default\_ami\_id | ID of the default worker group AMI |
246
-
| workers\_launch\_template\_arns | ARNs of the worker launch templates. |
247
-
| workers\_launch\_template\_ids | IDs of the worker launch templates. |
248
-
| workers\_launch\_template\_latest\_versions | Latest versions of the worker launch templates. |
249
-
| workers\_user\_data | User data of worker groups |
Copy file name to clipboardExpand all lines: docs/faq.md
+3-9Lines changed: 3 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
## How do I customize X on the worker group's settings?
4
4
5
-
All the options that can be customized for worker groups are listed in [local.tf](https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/local.tf) under `workers_group_defaults_defaults`.
5
+
All the options that can be customized for worker groups are listed in [local.tf](https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/modules/worker_groups/local.tf) under `workers_group_defaults_defaults`.
6
6
7
7
Please open Issues or PRs if you think something is missing.
8
8
@@ -61,12 +61,6 @@ You need to add the tags to the VPC and subnets yourself. See the [basic example
61
61
62
62
An alternative is to use the aws provider's [`ignore_tags` variable](https://www.terraform.io/docs/providers/aws/#ignore\_tags-configuration-block). However this can also cause terraform to display a perpetual difference.
63
63
64
-
## How do I safely remove old worker groups?
65
-
66
-
You've added new worker groups. Deleting worker groups from earlier in the list causes Terraform to want to recreate all worker groups. This is a limitation with how Terraform works and the module using `count` to create the ASGs and other resources.
67
-
68
-
The safest and easiest option is to set `asg_min_size` and `asg_max_size` to 0 on the worker groups to "remove".
69
-
70
64
## Why does changing the worker group's desired count not do anything?
71
65
72
66
The module is configured to ignore this value. Unfortunately Terraform does not support variables within the `lifecycle` block.
@@ -77,9 +71,9 @@ You can change the desired count via the CLI or console if you're not using the
77
71
78
72
If you are not using autoscaling and really want to control the number of nodes via terraform then set the `asg_min_size` and `asg_max_size` instead. AWS will remove a random instance when you scale down. You will have to weigh the risks here.
79
73
80
-
## Why are nodes not recreated when the `launch_configuration`/`launch_template` is recreated?
74
+
## Why are nodes not recreated when the `launch_configuration` is recreated?
81
75
82
-
By default the ASG is not configured to be recreated when the launch configuration or template changes. Terraform spins up new instances and then deletes all the old instances in one go as the AWS provider team have refused to implement rolling updates of autoscaling groups. This is not good for kubernetes stability.
76
+
By default the ASG is not configured to be recreated when the launch configuration changes. Terraform spins up new instances and then deletes all the old instances in one go as the AWS provider team have refused to implement rolling updates of autoscaling groups. This is not good for kubernetes stability.
83
77
84
78
You need to use a process to drain and cycle the workers.
Copy file name to clipboardExpand all lines: docs/spot-instances.md
+5-43Lines changed: 5 additions & 43 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,65 +22,27 @@ Notes:
22
22
- There is an AWS blog article about this [here](https://aws.amazon.com/blogs/compute/run-your-kubernetes-workloads-on-amazon-ec2-spot-instances-with-amazon-eks/).
23
23
- Consider using [k8s-spot-rescheduler](https://github.com/pusher/k8s-spot-rescheduler) to move pods from on-demand to spot instances.
24
24
25
-
## Using Launch Configuration
26
-
27
-
Example worker group configuration that uses an ASG with launch configuration for each worker group:
Launch Template support is a recent addition to both AWS and this module. It might not be as tried and tested but it's more suitable for spot instances as it allowed multiple instance types in the same worker group:
0 commit comments