TCP hostname routing using SNI

Server NGINX
1

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:

2

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.

3

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.