Open jacekn opened 1 month ago
This issue is currently awaiting triage.
If cloud-provider-aws contributors determine this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
What happened:
I deployed the controller and configured NLB type Service. The service was created in AWS with associated target group but the target group is empty
What you expected to happen:
I expected the
service-lb-controller
controller to populate the target groupHow to reproduce it (as minimally and precisely as possible):
I deployed the controller using manifest generated like this:
And used IAM policy from the docs. I then created the
Service
object like this:Once applied ELB was created together with health checks and TargetGroups. However target groups are empty. I also noticed that security group entries were not added.
Anything else we need to know?:
This used to work with in-tree controller. We disabled the in-tree and moved to external and the Service controller no longer works in the same cluster.
Logs show successful calls to retrieve node details from AWS, for example:
I also confirmed with CloudTrail that there are no permission error with API calls.
If I add nodes manually to the Target group they are removed from the Target group.
Environment:
kubectl version
):Ubuntu 20.04.6 LTS
uname -a
):5.15.0-1058-aws #64~20.04.1-Ubuntu SMP
kubeadm
/kind bug