Support for NLBs targeting ALBs

[gshutler]

A few weeks ago it was announced that NLBs could now use and Application Load Balancer-type Target Group (docs).

We are currently using the previously documented workaround involving Lambda which this feature is intended to replace and would love to switch to the new method.

[kishorj]

/kind feature

[kishorj]

@gshutler, thanks for bringing it to our attention. We have been considering this feature post v2.3.0 release.

[kurtbomya]

Oh this is critical for an architecture I'm working on!

[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

[jsokol89]

/remove-lifecycle stale

[sunild]

We're wanting this feature to get implemented as well. Our use case might be useful to others:

• We need static IP addresses so we are using an NLB
• We have been using an ALB and would like to continue with it for most of our traffic
• For the app the requires the static IP's:
  -- we let the NLB terminate TLS connections
  -- we redirect HTTP to HTTPS by manually adding the ALB as a target group for the NLB

This works well, as I don't have to do anything special other than create/add a target group to the NLB and avoids having to put something behind (or in front of) the NLB to redirect to HTTPS.

However, some event eventually causes the manual configuration to get removed. Implementing this feature will allow us to remove the problematic manual configuration.

[wallhided]

bump

[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