Open jrouly opened 1 year ago
Thanks for reporting the issue. Would you be able to provide a Go Heap Profile?
@alvinlin123 no, I no longer have the pod deployed as it continued to run OOM as described.
Do you have instructions or a link to documentation for gathering a Go Heap Profile?
I'm running an
aws-sigv4-proxy
sidecar along with opencost.io to proxy Prometheus metrics from an AMP workspace endpoint.I've granted the
aws-sigv4-proxy
container an obscene level of resources, and it's continuing to burn through them and run OOM as though no GC is active.I'm running this pod on EKS EC2 workers provisioned with Karpenter.