# Istio-proxy 's cpu request is excluded from cpu utilization of HPA

**URL:** https://discuss.kubernetes.io/t/istio-proxy-s-cpu-request-is-excluded-from-cpu-utilization-of-hpa/18121
**Category:** General Discussions
**Tags:** istio
**Created:** [November 17, 2021, 7:51am UTC](https://discuss.kubernetes.io/t/istio-proxy-s-cpu-request-is-excluded-from-cpu-utilization-of-hpa/18121 "2021-11-17T07:51:36Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![hebin7](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/hebin7/32/8950_2.png) [@hebin7](https://discuss.kubernetes.io/u/hebin7)
#### Post date: [November 17, 2021, 7:51am UTC](https://discuss.kubernetes.io/t/istio-proxy-s-cpu-request-is-excluded-from-cpu-utilization-of-hpa/18121/1 "2021-11-17T07:51:36Z")

</div>

hi, i am testing a performance of my service(myapp), and a little bit confused with the HPA result  
"  
kubectl get hpa | grep myapp  
myapp Deployment/myapp 81%/80% 2 2 2 7d23h

kubectl top pod myapp-85c77fbcd7-7ppxr --containers  
myapp-85c77fbcd7-7ppxr myapp 1775m 1091Mi  
myapp-85c77fbcd7-7ppxr leader-elector 1m 18Mi  
myapp-85c77fbcd7-7ppxr tap-agent 3m 7Mi  
myapp-85c77fbcd7-7ppxr istio-proxy 809m 114Mi

cpu request for containers as below:  
myapp 3G  
leader-elector 50m  
tap-agent 100m  
istio-proxy 2G (automatically injected, not static defined in deployment yaml)

noticed that the istio-proxy is auto injected, so the cpu request is not defined in myapp deployment yaml  
"

according to the above data, the HPA 81% almost equals to (1775m+1m+3m+809m) / (3G+50m+100m), in other words, the istio-proxy’s cpu request is not calculated in HPA

i don’t know why it happens, it’s a bug of k8s API ？