Releases: cloudposse/terraform-aws-eks-node-group
v2.6.1
🚀 Enhancements
Add instance, volume, network-interface as resource tag defaults @nitrocode (#132)
what
- Add instance, volume, network-interface as resource tag defaults
why
- Reasonable tagging defaults
references
- Closes #131 (comment)
- Other module also contains this as a default
Contributors
Assets 2
v2.6.0
Detailed monitoring @IkePCampbell (#126)
What did I do
- Add detailed monitoring flag to the launch template of EC2 nodes
Why did I do this
- Some compliance tools will flag nodes used by this module because they don't have detailed monitoring. This also allows metrics to be reported every minute as opposed to five minute intervals
Helpful references
Contributors
Assets 2
v2.5.0 IPv6 support, non-breaking changes expected
Upgrading to this version, if you have node_role_cni_policy_enabled set to true (the default), will cause a new IAM policy to be created and your existing node group IAM role to have its permissions updated. This will cause a transient interruption in the ability of the node to manage its network interface, but it should heal itself with no interruption to existing services. It may cause a short (some seconds) delay in being able to deploy new Pods.
references
- Documentation of recommended IPv6 permissions
- Third-party documentation of
AmazonEKS_CNI_Policy.
details
Contributors
Assets 2
v2.4.0
With this release, we end the use of pre-production (version 0.x) Semantic Versions for this module. Earlier releases have been re-released to make upgrading using semantic versions possible.
This release has a change that may trigger an update. The ebs_optimized input was added in v2.2.0 (and v0.27.2) with a default value of false. In this release, we change the default value to true, which is the value recommended by AWS and is the default value for most instance types.
Although this release contains a fix to generate the correct values for the tags (with keys of the form k8s.io/cluster-autoscaler/node-template/taint/$TAINT) that give a hint to the Cluster Auto Scaler about what taints would be applied to nodes when launched (prior to his release, the tag values were invalid), the tags are only effective when applied to the auto scaling group controlling the node group, and even with this release, this module still does not apply the tags to the auto scaling group. See aws/containers-roadmap#608 for more details.
Other changes:
- Add updated documentation for migration to V2.0.0
- Add tags to the output, supersedes and closes #112, closes #111
- Fix the tag value for Auto Scaler tags that indicate taints
For details, see PR #118
v0.28.1
git.io->cloudposse.tools update @dylanbannon (#114)
what and why
Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.
References
- DEV-143
🤖 Automatic Updates
chore(deps): update terraform cloudposse/security-group/aws to v1 @renovate (#117)
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/security-group/aws (source) | module | major | 0.4.3 -> 1.0.1 |
Contributors
Assets 2
v2.3.0 Requested features, general updates (#110)
Version 2.3.0 is exactly the same as v0.28.0 except for the version number, part of Cloud Posse's conversion to production Semantic Versioning for its Terraform modules.
This version is not recommended, because it includes the ebs_optimized input with a default value of false. The default has been changed to true in v2.4.0.
🚀 Enhancements
Requested features, general updates (#110)
what && why
Combine feature requests, bug fixes, and general updates into a single PR to reduce number of releases and also expedite requested changes to PRs.
- Allow
ami_type="CUSTOM", resolves #96, thank you @ingledl - Output ID and name of launch template, resolves #102, supersedes and closes #103, thank you @bwmetcalf
- Allow SSH access to provided
ssh_access_security_group_idswhether or not an SSH key is provided, resolves #108, thank you @bcbrockway - Update test framework, add test for
enabled=false, update workflows: general maintenance and conformity
🐛 Bug Fixes
Properly handle launch template changes, ensure SSH egress (#110)
what && why
Combine feature requests, bug fixes, and general updates into a single PR to reduce number of releases and also expedite requested changes to PRs.
- Change name of node group when launch template ID changes. Supersedes and closes #106, thank you @woz5999
- Allow all TCP egress to destinations where SSH ingress is allowed because that is required for SSH to work (usually not a problem because usually node groups allow all egress to all destinations)
Contributors
Assets 2
v0.28.0
🚀 Enhancements
Requested features, general updates (#110)
what && why
Combine feature requests, bug fixes, and general updates into a single PR to reduce number of releases and also expedite requested changes to PRs.
- Allow
ami_type="CUSTOM", resolves #96, thank you @ingledl - Output ID and name of launch template, resolves #102, supersedes and closes #103, thank you @bwmetcalf
- Allow SSH access to provided
ssh_access_security_group_idswhether or not an SSH key is provided, resolves #108, thank you @bcbrockway - Update test framework, add test for
enabled=false, update workflows: general maintenance and conformity
🐛 Bug Fixes
Properly handled launch template changes, ensure SSH egress (#110)
what && why
Combine feature requests, bug fixes, and general updates into a single PR to reduce number of releases and also expedite requested changes to PRs.
- Change name of node group when launch template ID changes. Supersedes and closes #106, thank you @woz5999
- Allow all TCP egress to destinations where SSH ingress is allowed because that is required for SSH to work (usually not a problem because usually node groups allow all egress to all destinations)
Contributors
Assets 2
v2.2.0 EBS optimization, tagging network interfaces
This version is not recommended, because it introduces the ebs_optimized input with a default value of false, which is a change from previous behavior and best practice. The default has been changed to true in v2.4.0.
Version 2.2.0 is exactly the same as v0.27.3 except for the version number, part of Cloud Posse's conversion to production Semantic Versioning for its Terraform modules..
🚀 Enhancements
Support tagging Network Interfaces @mholttech (#107)
what
Add support for tagging Network Interfaces with var.resources_to_tag
why
According to LaunchTemplateTagSpecificationRequest Documentation, Network Interfaces are now supported for tagging on creation.
references
support for ebs optimization in launch templates @jrowinski3d (#101)
what
- Enabled EBS Optimization in the launch template.
why
- Give the user ability to enable ebs optimization, default will be false. Of course the instance_type will need to be capable of doing so.
references
- closes #123
Contributors
Assets 2
v0.27.3
🚀 Enhancements
Support tagging Network Interfaces @mholttech (#107)
what
Add support for tagging Network Interfaces with var.resources_to_tag
why
According to LaunchTemplateTagSpecificationRequest Documentation, Network Interfaces are now supported for tagging on creation.
references
Contributors
Assets 2
v0.27.2
This version is not recommended, because it introduces the ebs_optimized input with a default value of false, which is a change from previous behavior and best practice. The default has been changed to true in v2.4.0. We recommend upgrading to v2.4.0 or later rather than upgrading to this version. No special effort is needed to upgrade to this version from v0.25.0 or later, or v2.0.0 or later. See the migration from v1 to v2 documentation for information on how to upgrade safely from earlier versions.
🚀 Enhancements
support for ebs optimization in launch templates @jrowinski3d (#101)
what
- Enabled EBS Optimization in the launch template.
why
- Give the user ability to enable ebs optimization, default will be false. Of course the instance_type will need to be capable of doing so.
references
- closes #123