Static External IP (AWS elastic IP)

[Vadim-Zenin]

Is your feature request related to a problem?
We need static external IP for AWS load-balancer.

Describe the solution you'd like
Would be nice if we could assign reserved AWS elastic IPs to the load-balancer.

[amznapei]

Hello, thanks for reporting this. Can you please clarify if this is referring to an ALB or NLB? Thank you.

[Vadim-Zenin]

Ideally would be for both ALB and NLB, like Internet <-> AWS NLB with elastic IP <-> AWS ALB <-> AWS EKS.
Minimum for NLB, like Internet <-> AWS NLB with elastic IP <-> AWS EKS.
Would be nice keep user's IP info...
P.S. AWS ALB does not support static IP even customers request it since many years ago. You could suggest any reasonable work around.

[zac-nixon]

Unfortunately we have not added support for ALB as a target of NLB (#2297).

Like you mention, NLB does support choosing the IP, and the controller supports it to. https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.10/guide/service/annotations/#eip-allocations

A solution to your problem is to set up an out of band NLB, have the LBC manage an ALB, and manually register the ALB into your NLB. This should be reasonably straight forward as you shouldn't need to manage the out of band NLB, while the LBC will do the heavy lifting of ensuring the ALB targets are correctly updated.

[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

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