You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I installed this on our cluster EKS K8S 1.11, and I noticed the istio-discover container using up large amounts of memory - approximately 20GB. Please look into this. It may be a memory leak
The text was updated successfully, but these errors were encountered:
I just run a cluster with >1000 ServiceEntires created sequentially (simple loop running curl)
dns-discovery was hitting 22mb-26mb res mem, so I wasn't able to reproduce this leak.
Can you please elaborate more about your environment, use-case, # serviceentries created - and anything else that might help me to spot this issue ?
We have 202 service entries. Use case is to do what dns-discovery is meant for- finding DNS names for all outbound traffic. We had it enabled for a few days before . See datadog screenshot. We have limits set in k8s so the container gets killed when memory usage goes too high.
I installed this on our cluster EKS K8S 1.11, and I noticed the istio-discover container using up large amounts of memory - approximately 20GB. Please look into this. It may be a memory leak
The text was updated successfully, but these errors were encountered: