Currently k8s ingress only supports HTTPS SNI.
I need k8s support for TLS SNI such that I can dynamically create TCP services with virtual server names and have a dynamically created TCP SNI reverse proxy dispatch connections to the correct k8s service.
I see that the linked-tcp beta is available and supports SNI. I see that linked-tcp integrates with the k8s API via namerd. I see some info on configuring namerd for k8s.
What I don’t see is the full path that results in the dynamic provisioning of TCP SNI reverse proxies for k8s services.
Is this something that linked-tcp can do? Has anyone integrated linked-tcp with k8s as a TCP SNI load balancer exposed via a k8s service loadbalancer on AWS?