Existing targets removed when creating TargetGroupBinding for exisitng NLB TG

[mbeaucha]

Describe the bug I have existing NLB and target groups using IP target mode. The TGs have existing targets in them from another deployment mechanism (in this case an ECS service). I defined/deployed a new TargetGroupBinding to add the same type of service under EKS, and when doing so all the existing targets in the TG are removed, and only the TargetGroupBinding targets are present.

Steps to reproduce Create NLB & TGs with IP mode Add targets to TG by some other means (manual, ECS, etc) Deploy TGB under EKS, see all previous targets removed.

Expected outcome I would expect the new targets from the TargetGroupBinding to be added to the TG without affecting the other registered targets.

Environment

• AWS Load Balancer controller version - 2.4.1
• Kubernetes version - 1.22
• Using EKS (yes/no), if so version? Yes (1.22)

Additional Context: I'm attempting to develop a migration of my system from ECS to EKS while re-using the ELB resources, both for seamless transition reasons, and because aws-load-balancer-controller Service annotations don't have enough flexibility yet to recreate my NLBs and TGs as currently configured.

[kishorj]

@mbeaucha, the controller assumes exclusive ownership of the targetgroup targets, so it will remove the existing targets if they are not part of the deployment (for ip targets), or the k8s cluster nodes for instance targets.

[wuyudian1]

Users should have the right to choose whether to enable this feature。

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.