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

[EKS] [request]: EKS Managed Nodes should allow attaching LB target groups #728

Closed
yann-soubeyrand opened this issue Jan 28, 2020 · 1 comment
Labels
Proposed Community submitted issue

Comments

@yann-soubeyrand
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request

When creating an EKS managed node group, one should be able to set a list of LB target groups which the populated nodes would attach to. At the moment, one has to figure out which autoscaling group has been created for the managed node group and edit it to set the desired target groups. I guess this is an unsupported operation and that it could break if a new autoscaling group is created for the node group (node groups' resources.autoScalingGroups attribute being a list hints me that it could happen).

Which service(s) is this request for?

EKS

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?

We've a node group dedicated to ingress controllers which we'd like to attach to two target groups (http and https) which are the destination of the two listeners (tcp 80 and tcp 443) of our internet facing NLB.

Are you currently working around this issue?

At the moment, we manually edit the generated autoscaling group to attach the target groups, but we suspect this is a fragile setup and we can't rely on a fragile setup for such a critical part of our cluster.

Additional context

This request may be closely related to #609.

@yann-soubeyrand yann-soubeyrand added the Proposed Community submitted issue label Jan 28, 2020
@mikestef9
Copy link
Contributor

Closing as a duplicate of #709

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Proposed Community submitted issue
Projects
None yet
Development

No branches or pull requests

2 participants