TCP hostname routing using SNI

We need TCP (not http) hostname routing for an environment we are
creating
using k8s and ingress with the nginx ingress controller. We are trying
to
figure out if there is a way to create an nginx server with a config
that
will route TCP calls to a single host:port to different host:port combos
based on the hostname held in the SNI information.

Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,267677,267677#msg-267677

On Fri, Jun 17, 2016 at 2:48 PM, jordan.davidson <
[email protected]> wrote:

We need TCP (not http) hostname routing for an environment we are creating
using k8s and ingress with the nginx ingress controller. We are trying to
figure out if there is a way to create an nginx server with a config that
will route TCP calls to a single host:port to different host:port combos
based on the hostname held in the SNI information.

This isn’t to say that there’s not a fully-formed module, but just
wanted
to point out that the nginx+lua extensions allow you to get at that
information. And then you could presumably use the balancer-by-lua stuff
to
route.

Hello,

On 6/18/16 12:48 AM, jordan.davidson wrote:

We need TCP (not http) hostname routing for an environment we are creating
using k8s and ingress with the nginx ingress controller. We are trying to
figure out if there is a way to create an nginx server with a config that
will route TCP calls to a single host:port to different host:port combos
based on the hostname held in the SNI information.

Currently the stream (tcp/udp lb) module misses this feature.
However, we do have it in the short-term roadmap and hope to have it
implemented more or less soon.


Maxim K.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs