Multiple aws-load-balancer-controllers being able to share a single ALB

[krishgu]

Does the AWS LB Controller support sharing a single ALB with multiple EKS's?

The tags that are seen on the load-balancer are:

Tag	Value
ingress.k8s.aws/resource	LoadBalancer
ingress.k8s.aws/stack	alb-name
elbv2.k8s.aws/cluster	cluster1-name

Does the elbv2.k8s.aws/cluster tag's value be a comma-separated set of values? How is it used in the "reconciliation" process by the AWS LB Controller?

Thanks.

[kishorj]

@krishgu, the controller assumes exclusive ownership over the ALB and the resources it creates. Currently, a single LB cannot be shared across multiple clusters.

The current option in your case is to create the ALB, listener rules and the target group outside of the controller. For multiple clusters, you'd use weighted target groups so there is a target group for each cluster. Then for each weighted target group, you can create TargetGroupBinding on the respective clusters. The controller keeps the target group up-to-date based on your backend service configuration.

[kishorj]

@krishgu, we currently don't have this feature in the immediate roadmap as it is difficult to share the load balancer level config between multiple controllers. There is a possibility of merging the listener rules configuration and utilizing weighted target groups to forward traffic to targets in different clusters.

[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.