Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Propagate ami_type to self-managed node group; allow using ami_type only #3030

Conversation

bryantbiggs
Copy link
Member

Description

  • Propagate the ami_type down to the self-managed nodegroup. This allows users to specify just the ami_type instead of needing to specify the ami_type and the platform (which is redundantly annoying). The platform functionality is still preserved for backwards compatibility until its removed in the next major version release
  • Fix the cluster_service_cidr output; previously it would output either the IPv4 CIDR or null, which is incorrect for IPv6 clusters

Motivation and Context

  • This simplifies and unifies the user experience across both EKS managed node groups and self-managed node groups, it also allow users to opt into the v21 functionality now instead of waiting which will future proof their configurations

Breaking Changes

  • No; validated by deploying EKS managed node group and self-managed node group examples on master and then switching to this branch to check the diff

How Has This Been Tested?

  • I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects
  • I have executed pre-commit run -a on my pull request

@bryantbiggs bryantbiggs requested a review from antonbabenko May 7, 2024 19:12
ssm_cluster_version = var.cluster_version != null ? var.cluster_version : ""

# TODO - Temporary stopgap for backwards compatibility until v21.0
ami_type_to_user_data_type = {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in v21, we can look at consolidating these repeated lookup maps in another helper sub-module like the user-data. but for now, a little bit of duplication is ok while we roll it out and ensure we maintain backwards compatibility

@bryantbiggs bryantbiggs merged commit 74d3918 into terraform-aws-modules:master May 8, 2024
17 checks passed
@bryantbiggs bryantbiggs deleted the feat/self-managed-ami-type branch May 8, 2024 12:04
antonbabenko pushed a commit that referenced this pull request May 8, 2024
## [20.9.0](v20.8.5...v20.9.0) (2024-05-08)

### Features

* Propagate `ami_type` to self-managed node group; allow using `ami_type` only ([#3030](#3030)) ([74d3918](74d3918))
@antonbabenko
Copy link
Member

This PR is included in version 20.9.0 🎉

Copy link

github-actions bot commented Jun 8, 2024

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants