How to gather a heap and cpu profiler from istio-proxy v1.1 container

Solution Verified - Updated -

Issue

Istio-proxy container (Envoy sidecar) is consuming huge amounts of memory and/or CPU and can't troubleshoot it using logs only.
Envoy sidecar container is getting OOM Killed.

Environment

  • OpenShift Container Platform 4.5+
  • Red Hat Service Mesh v1.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content