-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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: Add support for enabling addons before data plane compute is created #2478
feat: Add support for enabling addons before data plane compute is created #2478
Conversation
@@ -85,7 +85,8 @@ resource "aws_eks_cluster" "this" { | |||
aws_iam_role_policy_attachment.this, | |||
aws_security_group_rule.cluster, | |||
aws_security_group_rule.node, | |||
aws_cloudwatch_log_group.this | |||
aws_cloudwatch_log_group.this, | |||
aws_iam_policy.cni_ipv6_policy, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this addition now allows the resources to be cleaned up properly when users elect to create the IPv6 policy with the module
create_duration = var.dataplane_wait_duration | ||
|
||
triggers = { | ||
cluster_name = aws_eks_cluster.this[0].name |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
because all of these would trigger a downstream update, they make valid triggers here to ensure the nodegroups/Fargate profiles wait for this duration before proceeding
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I have just a minor suggestion to improve the understandability of it.
… output used downstream
…rraform-aws-eks into feat/addon-before-compute
## [19.9.0](v19.8.0...v19.9.0) (2023-02-17) ### Features * Add support for enabling addons before data plane compute is created ([#2478](#2478)) ([78027f3](78027f3))
This PR is included in version 19.9.0 🎉 |
@@ -19,6 +19,25 @@ locals { | |||
} | |||
} | |||
|
|||
# This sleep resource is used to provide a timed gap between the cluster creation and the downstream dependencies |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any documented reason we cannot use a depends_on
object on all compute modules referencing aws_eks_addon.before_compute
? Is this purely to avoid module dependencies?
If there was an actual dependency in place, there could be additional benefits (e.g. creating the VPC CNI with IRSA and eliminating the need for removing any instance roles after cluster creation). Anecdotally cluster_addon
creation is incredibly variable (I've seen it finish in seconds, and sometime in minutes).
The secondary reason I ask is concerns over downstream dependencies on deletion.
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. |
Description
Motivation and Context
Breaking Changes
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request