Re: [kubernetes-users] Load balancer drops backend while leaving frontend connected

No this is during regular operation. On Wed, Apr 4, 2018 at 11:39 AM, 'Nicks' via Kubernetes user discussion and Q wrote: > Did you remove a node from the cluster? Even if a node was in the cluster > and didn't run any workload, it could still be used to proxy

Re: [kubernetes-users] Load balancer drops backend while leaving frontend connected

Did you remove a node from the cluster? Even if a node was in the cluster and didn't run any workload, it could still be used to proxy connections from the LB and the service pod. On Friday, March 30, 2018 at 7:42:42 AM UTC-7, Tyler Johnson wrote: > > Environment: GKE 1.7.12-gke.1 > I believe

Re: [kubernetes-users] Load balancer drops backend while leaving frontend connected

Environment: GKE 1.7.12-gke.1 I believe the ingress controller is GLBC[1] [1] https://github.com/kubernetes/ingress-gce On Thu, Mar 29, 2018 at 11:56 PM, 'Tim Hockin' via Kubernetes user discussion and Q wrote: > Which environment and which Ingress

Re: [kubernetes-users] Load balancer drops backend while leaving frontend connected

Which environment and which Ingress controller? On Thu, Mar 29, 2018 at 8:42 PM Tyler Johnson wrote: > Is it possible that an HTTP load balancer (auto-configured as part of an > Ingress) could occasionally drop backend connections while leaving the > frontend

[kubernetes-users] Load balancer drops backend while leaving frontend connected

Is it possible that an HTTP load balancer (auto-configured as part of an Ingress) could occasionally drop backend connections while leaving the frontend connected? I'm running a websocket backend service (the backend-service timeout is high) and on very rare occasions I'll see the service pod