-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
(aws-eks) Managed Node Group propagate the tags to Auto Scaling Group #20133
Comments
CC @pahud |
Thanks @yws-ss for the detailed description. I believe this is a very common scenario for managed nodegroups with the Kubernetes Cluster Autoscaler capabilities and eksctl has already built in the tags propagation via the SDK call under the hood. It seems to me that we might make it a default or optional behavior for the tags propagation through a CDK custom resource for the hack. wdyt @otaviomacedo ? If you agree maybe I can invite someone from the community for the PR. cc @peterwoodworth and @ryparker |
@pahud Yes, it seems the only way to solve this is with a custom resource. |
Is there any update on this? I'm running into something similar with the GO cdk: myCluster.AddNodegroupCapacity(jsii.String("my-nodegroup"), &eks.NodegroupOptions{
InstanceTypes: &[]ec2.InstanceType{
ec2.NewInstanceType(jsii.String("m5.xlarge")),
},
MinSize: jsii.Number(5),
AmiType: eks.NodegroupAmiType_BOTTLEROCKET_X86_64,
NodeRole: nodeRole,
})
// Further down with the entire stack
awscdk.Tags_Of(stack).Add(jsii.String("Name"), jsii.String("my-custom-nodes"), &awscdk.TagProps{
ApplyToLaunchedInstances: jsii.Bool(true),
}) This tag is not propagated to the instances that get launched through the node-groups auto-scaling group. |
This is still a feature request of EKS |
closing in favor of #29280 (comment) |
|
Describe the feature
Currently, there have no solution can add the tags to Auto Scaling Group which managed by Managed Node group through CDK construct. The tags on Auto Scaling Group can be used in many place, such as: Cluster AutoScaler or billing organization.
Use Case
There have a scenario need this feature. Per Cluster Autoscaler document mentioned, if the node group want to scale up from 0, we need to add the resources tags on the auto scaling group to let Cluster Autoscaler discover them. Such as:
Base on current "NodeGroup" construct [2], we could not apply tags from it because managed node group tags currently cannot bring to auto scaling group. Also, "NodeGroup" construct would not return any auto scaling group information which could let us use other function such as "Tags" to directly add tag to auto scaling group.
Proposed Solution
Currently, eksctl use AWS API at the backend to propagate the managed node group to auto scaling group #5002. and provide the parameter in YAML configuration.
Other Information
No response
Acknowledgements
CDK version used
latest
Environment details (OS name and version, etc.)
Linux
The text was updated successfully, but these errors were encountered: