Connection getting dropped immediately in TCPIngress

[tarunmittal24]

Hi Guys,

I have setup the TCP Ingress, here are the following config

tcp-ingress.yaml

apiVersion: configuration.konghq.com/v1beta1
kind: TCPIngress
metadata:
  name: redis-tcp-ing
  namespace: redis
spec:
  rules:
  - backend:
      serviceName: redis-svc
      servicePort: 6379
    port: 6379

service.yaml

apiVersion: v1
kind: Service
metadata:
  name: redis-svc
  namespace: redis
spec:
  ports:
  - port: 6379
    protocol: TCP
    targetPort: 6379
  selector:
    app: redis
  type: ClusterIP

I am trying to do the telnet and it is working fine as expected

But if my background service is down, it is showing connected and then got dicsonnected error

Does anyone have ever faced it, or i am missing something.

[chronolaw]

@randmonkey , could you take a look at this? thanks.

[randmonkey]

@tarunmittal24 What is your "background service"? Does it mean your redis clusters used as the backend? I think the behavior is reasonable if your redis service is down because Kong proxy cannot reach the backend services. What is your expected behavior in this scenario?

[tarunmittal24]

@randmonkey , background service is redis service which is sending traffic to the single redis pod, but as you can see, it first got connected and then it is disconnecting or breaking the connection see the screenshot above. [connection closed by foreign host] comes automatically.

Question here is why it is happening in this way, because if the server is not reachable it will give like this, will stuck for sometime and then got timeout, just for example i am giving like this.

[ADD-SP]

@tarunmittal24 I think this is an expected behavior, Kong Gateway did L4 proxy, telnet connected to Kong Gateway first, and a connection was established between the telnet and Kong Gateway, and then Gateway chose a backend (which is your Redis server) and tried to establish a connection between the Kong Gateway and your Redis server. However, since the Redis was down, the Gateway was unable to establish the connection, so the Gateway shutdown the connection between telnet and Kong Gateway.

[tarunmittal24]

sure @ADD-SP , thanks for the clarification.