You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
I would like to use a pre-existing NLB with a k8s service running in an EKS-cluster with auto-mode enabled.
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?
Because I would like my front-end Network Load Balancer to have a lifetime separate from that of the EKS control-plane, I currently provision the NLB and Target Group myself, and then directly create a TargetGroupBinding resource to register appropriate services with the NLB. This is a documented feature of the aws-load-balancer-controler here: https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.11/guide/targetgroupbinding/spec/
I would like to continue this pattern with an EKS auto-mode cluster.
Following the public documentation listed above does not work because the k8s resource-group elbv2.k8s.aws/v1beta1 is not available.
There is a similar resource in eks.amazonaws.com/v1 which appears to be compatible at first, but I haven't found any documentation that what I'm doing is supported.
If I try to create a TGB in eks.amazonaws.com/v1 I get the following errors in CloudTrail for the RegisterTargets action:
User: arn:aws:sts::<my account id>:assumed-role/<my cluster role name>/aws-go-sdk-1735434588572399672 is not authorized to perform: elasticloadbalancing:RegisterTargets on resource: <my target group> because no session policy allows the elasticloadbalancing:RegisterTargets action
Presumably the role-session-policy is enforcing some constraint I don't know about (and even if I did know how to satisfy this constraint I would want some documentation or signal that this is supported).
Are you currently working around this issue?
How are you currently solving this problem? Avoiding auto-mode.
Additional context
Anything else we should know?
Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)
The text was updated successfully, but these errors were encountered:
Community Note
Tell us about your request
I would like to use a pre-existing NLB with a k8s service running in an EKS-cluster with auto-mode enabled.
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?
Because I would like my front-end Network Load Balancer to have a lifetime separate from that of the EKS control-plane, I currently provision the NLB and Target Group myself, and then directly create a TargetGroupBinding resource to register appropriate services with the NLB. This is a documented feature of the aws-load-balancer-controler here: https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.11/guide/targetgroupbinding/spec/
I would like to continue this pattern with an EKS auto-mode cluster.
Following the public documentation listed above does not work because the k8s resource-group
elbv2.k8s.aws/v1beta1
is not available.There is a similar resource in
eks.amazonaws.com/v1
which appears to be compatible at first, but I haven't found any documentation that what I'm doing is supported.If I try to create a TGB in
eks.amazonaws.com/v1
I get the following errors in CloudTrail for the RegisterTargets action:Presumably the role-session-policy is enforcing some constraint I don't know about (and even if I did know how to satisfy this constraint I would want some documentation or signal that this is supported).
Are you currently working around this issue?
How are you currently solving this problem? Avoiding auto-mode.
Additional context
Anything else we should know?
Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)
The text was updated successfully, but these errors were encountered: