aws / aws/aws-application-networking-k8s

Duplicate Target Groups

Open
#698 5 comments 0 reactions 0 assignees View on GitHub
discussion needs investigation
Dominant language
Go
Stars
278
Forks
85
PR merge metrics
No merged PRs in 30d

Description

I installed the aws-application-networking-k8s into my EKS 1.29 cluster so that we can start using services between our clusters. For some reason it's creating two target groups, one with targets and one without. The controller is attaching our Lattice service to the target group with no targets. When I check the controller logs it seems to be running the reconciliation process with no errors.

We need figure out whats happening with the Lattice Service -> Lattice Target group assignment.

These are the two CRD/Controller verions

[https://github.com/aws/aws-application-networking-k8s/releases/tag/v1.1.0 ](https://github.com/aws/aws-application-networking-k8s/releases/tag/v1.1.0)

https://github.com/kubernetes-sigs/gateway-api/releases/tag/v1.2.1

Contributor guide

Open the contributing guide

Research direction

The issue names no source files, tests, manifests, or entry points. Start by reproducing the EKS 1.29 behavior with aws-application-networking-k8s v1.1.0 and Gateway API v1.2.1, then compare the controller logs and the two created target groups. Done means identifying why the Lattice Service attaches to the empty target group and confirming the corrected assignment.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, go, kubernetes
Domain
cloud, devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.