I’m using kong ingress controller for our kubernetes cluster. I’m looking for a way to connect GitLab Shell component to a container that requires TCP traffic to pass through on port 22.
I’ve been searching for documentation or solution. I saw that this is possible using nginx-ingress-controller, they have support for exposing tcp service using the flag --tcp-services-configmap. See below documentations.
Is there a similar way to do it using kong ingress controller? Thanks
I am using the latest Controller and I followed this document to setup TCPIngress for my db-less installation. But I am getting the below error in pod and it goes to CrashLoopBackOff status.
F0406 05:28:38.611721 1 main.go:185] making HTTP request: Get “https://localhost:8444/”: dial tcp [::1]:8444: connect: connection refused
Then I tried to expose the port 8444 by adding it to the service. but still it gives the same error in the pod’s log.
I am using kong in db-less mode as well. I would like use the TCPIngress resource because now is hard to manage the TCP publications and I must create LoadBalancers for each (in some cloud providers there is limitations) or install another ingress controller implementation which support this.
Hi, I want to check if there is any update on this topic. I’m using Kong Ingress 0.10.0 with Kong 2.1.4 today but TCPIngress does not work with DB-less mode.
Thanks for asking. I finally get it worked but I still have three questions:
I followed the tcp ingress guide and created a minikube cluster for testing. Then I realized the Proxy IP(eg: http://192.168.99.100:31350) cannot be used in telnet command thus telnet $PROXY_IP 9000 will not return the expected response. I also tried telnet 192.168.99.100 9000 but only got Trying 192.168.99.100... telnet: connect to address 192.168.99.100: Connection refused telnet: Unable to connect to remote host. So I assume the tcpingress guide will not work with minikube, right?
I then used kube cluster on AWS and the tcpingress guide works fine. The only question I have here is that I see no address bind to the TCPIngress when I run kubectl get TCPIngress
I tried to follow the guide and added new ports and then found out port 389 failed while port 9001 succeed. After I adding port 389, I got an error in pod/ingress-kong immediately
Warning BackOff 7s (x3 over 12s) kubelet, ip-172-20-47-181.us-east-2.compute.internal Back-off restarting failed container Warning Unhealthy 6s kubelet, ip-172-20-47-181.us-east-2.compute.internal Readiness probe failed: Get http://100.124.0.4:10254/healthz: dial tcp 100.124.0.4:10254: connect: connection refused Warning Unhealthy 2s kubelet, ip-172-20-47-181.us-east-2.compute.internal Liveness probe failed: Get http://100.124.0.4:10254/healthz: dial tcp 100.124.0.4:10254: connect: connection refused
So I want to ask if there is any restriction about the available ports in kong ingress?
Thanks,
I’m using Kong Ingress 0.10.0 with Kong 2.1.4, Kube Server version: v1.18.9. We also use terraform 0.11.11 for creating the kube cluster.
The Proxy_IP show up under Ingress not tcpingress