bragi92
bragi92
I have validated the changes in this PR by building it locally and deploying it on a VM while leaving the client_id filed empty (""). I believe this is good...
@dhleemarchex Are you looking to make the changes asked here? I can help with that too if you give me access to your fork to make contributions.
Sounds good @bboreham I'll open a new PR for this.
@vaibhav2107 I missed this in the post initially. The metric value I'm seeing as impossibly high is for the conainer.
containerd version -> containerd://1.6.4+azure-4 I am making a request to the `/stats/summary` endpoint on the node and looking for all the `usageNanoCores` values for each container and getting the impossibly...
I am going to try using the `only_cpu_and_memory=true` flag and see if the issue reproduces. Its very inconsistent so will update the issue with my findings once I have run...
Looks like the issue is still happening after updating the call to use the only_cpu_and_memory flag: 
Yes, I still have the repro in my cluster with the above YAML file. It only happens randomly for some cadvisor calls. Most of them return the proper values.
Hey @jsturtevant I have tried querying cadvisor using ```https://{nodeIP}:10250/stats/summary``` from within the container but it seems like this is only happening on random times and I didn't get the impossibly...
@jsturtevant Do we know if there is any mitigation for this issue that I can apply?