LoadBalancerNegWithoutHealthCheck causes dropped requests

[dermasmid]

When a new pod gets added, it gets marked healthy right away instead of waiting for the lb to mark it so.
anyone else seeing this?

Pod is in NEG "Key{\".....", zone: \"us-central1-f\"}". NEG is not attached to any BackendService with health checking. Marking condition "cloud.google.com/load-balancer-neg-ready" to True.

[rosmo]

Oh, this has nothing to do with Autoneg. I guess we need more information, but there are quite a few different health checks involved here (internal Kubernetes, load balancer healthchecks, etc). It's a fairly complicated problem - which I haven't seen really properly explained anywhere.