I've been trying to diagnose this issue for several days and have a pretty good picture what is happening, but still no idea why.

The symptom is requests to different Services with failing TCP network connection (EHOSTUNREACH, ECONNREFUSED, Connection reset by peer, No route to host, Connection refused, Connection timed out, etc) from other Pods. I've gone through logs in detail around one incident and for some reason no request was sent downstream to any of the Pods in the ReplicaSet backing the Service for 9 seconds.

I couldn't find any obvious signs why traffic to Pods stopped or restarted and this what I'd need some help with, not really sure where else to look or what to try.

There are a few more things which might be relevant:

  • Readiness probe requests went through and responded to successfully every second - these were the only requests reaching Pods
  • DNS resolution seems to be working as some Pods logged being unable to connect to the Service's resolved IP
  • Cluster logs showing io.k8s.core.v1.endpoints.update API calls around the outage, but Node IPs were in addresses (not notReadyAddresses) list
  • The issue seems to happen more often when pods are being destroyed (or created) so deployment, auto-scaling or Node pre-emption, but it did happen with a stable number of replicas too
  • We're running Kubernetes 1.15 and 1.16 on GKE, unfortunately not VPC-native (alias IP) as the clusters were created a few years ago
  • We don't have Istio or any other service mesh running, but I'm very tempted now

Thanks in advance for any suggestions!

  • Is it possible for you to provide a detailed description of your configuration so that it can be reproduced on other test GKE cluster ? Does it happen on both 1.15 and 1.16 GKE clusters ?
    – mario
    Oct 23, 2020 at 16:42
  • @mario I'm not sure if it would be possible to share a simple reproduction as it's difficult to reliably reproduce even with the actual clusters and services. It does happen on both versions. At this point I was just looking for possible causes to explore, ie why would a Service not send traffic to healthy pods and how to diagnose.
    – dain
    Oct 23, 2020 at 19:52
  • 1
    Hi @dain, I think in such situation it makes sense to contact GCP Support. If this is something hard or even impossible to easily reproduce on another GKE test cluster, it would be rather difficult to find appropriate help here.
    – mario
    Oct 30, 2020 at 10:25
  • Thanks @mario, I'm trying now to switch over to new, VPC-native clusters to see if that solves the problem. Even if not, at least I can start sampling network traffic with flow logs and hopefully understand the issue.
    – dain
    Oct 30, 2020 at 20:54
  • @dain Did you solve this issue? Does VPC-native cluster help? Do you still encounter this issue? Any steps to replicate?
    – PjoterS
    Feb 24, 2021 at 9:16

1 Answer 1


This issue is very complex and hard to replicate. It would required to replicate this issue with OPs environment with the same configuration.

If you encounter situation which might be caused by Bug on GKE or GCP and it's almost impossible to replicate (like this one), best approach would be to reach Google Support for deep analysis.

Alternatively you could reach Public Issue Tracker.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.