Hello there, Seems we are facing a quite weird issue where TCP connections are getting closed forcefully.
How have we seen this? Our scripts speak to a service that is an API. From time to time, there are connections that scripts see this error: ConnectionError 'Remote end closed without response' and in the API we see that the error comes from the client closing the connection without waiting. So our guess, is that there is some problem in the middle. The only thing in the middle is kube-proxy and the IPtables. IPtables are okay, and kube-proxy doesn't show anything strange in its logs.... Also, the funny thing is that we only see this in one of the namespaces (we have the same setup in both namespaces). This is happening in a AWS cluster created with Kops and running K8s 1.8. We haven't updated yet to 1.9 as this is our production cluster. -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
