github-mirrors/terraform-aws-eks
1
0
Fork 0
mirror of https://github.com/ysoftdevs/terraform-aws-eks.git synced 2026-04-24 17:48:26 +02:00
Code Issues Packages Projects Releases Wiki Activity

chore: Update user data docs to correct mistake of showing bootstrap_extra_args when prepending user data (default AMI) (#1773)

Browse Source
This commit is contained in:
Bryant Biggs
2022-01-12 14:23:45 -05:00
committed by GitHub
parent 5818de1fbd
commit 78555e1a13
3 changed files with 5 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
examples/user_data/main.tf
View File

@@ -19,14 +19,7 @@ module "eks_mng_linux_additional" {
source = "../../modules/_user_data"
pre_bootstrap_user_data = <<-EOT
echo "foo"
export FOO=bar
EOT
bootstrap_extra_args = "--kubelet-extra-args '--node-labels=node.kubernetes.io/lifecycle=spot'"
post_bootstrap_user_data = <<-EOT
echo "All done"
export CONTAINER_RUNTIME="containerd"
EOT
}
@@ -41,11 +34,11 @@ module "eks_mng_linux_custom_ami" {
enable_bootstrap_user_data = true
pre_bootstrap_user_data = <<-EOT
echo "foo"
export FOO=bar
export CONTAINER_RUNTIME="containerd"
export USE_MAX_PODS=false
EOT
bootstrap_extra_args = "--kubelet-extra-args '--node-labels=node.kubernetes.io/lifecycle=spot'"
bootstrap_extra_args = "--container-runtime containerd --kubelet-extra-args '--max-pods=20 --instance-type t3a.large'"
post_bootstrap_user_data = <<-EOT
echo "All done"

1
modules/_user_data/README.md
View File

@@ -21,7 +21,6 @@ When using an EKS managed node group, users have 2 primary routes for interactin
```hcl
pre_bootstrap_user_data = "..."
bootstrap_extra_args = "..."
```
2. If the EKS managed node group does utilize a custom AMI, then per the [AWS documentation](https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html#launch-template-custom-ami), users will need to supply the necessary bootstrap configuration via user data to ensure that the node is configured to register with the cluster when launched. There are two routes that users can utilize to facilitate this bootstrapping process:

2
modules/_user_data/main.tf
View File

@@ -28,7 +28,7 @@ locals {
cluster_endpoint = var.cluster_endpoint
cluster_auth_base64 = var.cluster_auth_base64
# Optional - is appended if using EKS managed node group without custom AMI
# cluster_service_ipv4_cidr = var.cluster_service_ipv4_cidr # Not supported yet: https://github.com/bottlerocket-os/bottlerocket/issues/1866
# cluster_service_ipv4_cidr = var.cluster_service_ipv4_cidr # Bottlerocket pulls this automatically https://github.com/bottlerocket-os/bottlerocket/issues/1866
bootstrap_extra_args = var.bootstrap_extra_args
}
)) : ""