aws-load-balancer-controller icon indicating copy to clipboard operation
aws-load-balancer-controller copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

[Feature] TargetGroupBinding for TargetGroup outside of ALB Controller's VPC

Open KamikazeZirou opened this issue 2 years ago • 3 comments

Is your feature request related to a problem?

I'd like to bind pods to a TargetGroup in a VPC outside the EKS cluster. A similar feature was added in #1862, but it does not work in my case.

The infrastructure configuration I would like to build is shown below. image

When registering the pod's IP address to the TargetGroup that is in a VPC outside the EKS cluster, it is necessary to set "all" for the availability zone. In the current implementation, "all" is set if the pod's IP address is not in the VPC CIDRs configured in the ALB Controller. In my case, the VPC of the ALB Controller is the same as the VPC of the EKS cluster, so "all" is not set.

Describe the solution you'd like

Set "all" to the availability zone if the pod's IP address is in the VPC of the TargetGroup.

Describe alternatives you've considered

The problem can be avoided by deploying two ALB Controllers on one cluster. However, I do not know if it is possible to deploy two ALB Controllers.

Note

I think that this issue is the same as aws/eks-charts#745.

KamikazeZirou avatar May 13 '22 08:05 KamikazeZirou

@KamikazeZirou, are the VPCs in the same account or different accounts?

kishorj avatar May 24 '22 21:05 kishorj

@kishorj

They are in the same account.

KamikazeZirou avatar May 25 '22 01:05 KamikazeZirou

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 avatar Aug 23 '22 01:08 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 avatar Nov 30 '22 00:11 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 avatar Dec 30 '22 00:12 k8s-triage-robot