Open gshutler opened 3 years ago
/kind feature
@gshutler, thanks for bringing it to our attention. We have been considering this feature post v2.3.0 release.
Oh this is critical for an architecture I'm working on!
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
We're wanting this feature to get implemented as well. Our use case might be useful to others:
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.
bump
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the PR is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
This too is a feature I could use. create a nlb and define the target for a port to a alb. Is this still on the roadmap?
Also have interest in this feature. It is a surprise when looking to configure the NLB that I can use other target types but not ALB.
This is would be ideal for architectures using private link and API gateway VPC link, such as: https://aws.amazon.com/blogs/networking-and-content-delivery/application-load-balancer-type-target-group-for-network-load-balancer/
Currently looks like we will have create a shared NLB and target group + binding in terraform to achieve this.
NLB/TargetGroup CRDs or a dummy service to chain NLB -> ALB could be an option
We would also like to use this feature. Any updates ? Anyone actively working on this ? Issue is open for 900 days
+1 for this feature to create NLB and set target group to an ALB.
+1 It must be implemented.
+1 I must configure NLB either using Terraform or manually. It is not straightforward with Kubernetes.
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.