[Feature request] Reference a targetGroup by name in `TargetGroupBinding`

[MarcusDunn]

EDIT: Right after creating this, I noticed (#2373, which has a similar motivation. Unsure if this should be closed as a duplicate.)

Is your feature request related to a problem? I manage my load balancer externally (Terraform) and use TargetGroupBinding's to attach services to it. Adding a new service and binding it is a long and somewhat manual process.

Currently, I have to

1. Run Terraform to add new target groups
2. Wait for it to complete
3. Find the ARNs of the allocated target groups
4. Add TargetGroupBindings to my cluster.

Describe the solution you'd like Reference target groups by name (#2655)

I would prefer to be able to run Terraform and add TargetGroupBinding in a single step.

I noticed there was no issue attached to the PR, so I figured I would make one to:

• Express my interest in the feature and allow others to do the same in a more discoverable place than a two-year-old PR. Or,
• Find out if someone more clever than me has a better solution.

Describe alternatives you've considered

• Continue my multi-step, somewhat manual process.
• Attempt to automate the addition of TargetGroupBinding outside of Terraform and Kubernetes lifecycles.

[shraddhabang]

Hello @MarcusDunn , This does make sense and adds value to the controller. We will try to take a revisit this and take look at the open PR.

[anthisfan]

We have also been paying close attention to this feature PR for two years and are looking forward to its implementation.

[fatmcgav]

#2655 has been rebased as #3903 👍

[fatmcgav]

This has been released in 2.11.0

[k8s-triage-robot]

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

This bot triages un-triaged 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:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue 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.

This bot triages un-triaged 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:

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

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

/lifecycle rotten

[fatmcgav]

/close

[k8s-ci-robot]

@fatmcgav: Closing this issue.

In response to this:

/close

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-sigs/prow repository.