Hi @daniellavoie. Thanks for your PR.

I'm waiting for a google member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Hello @iwankgb @bobbypage, sorry to ping you directly. Could you help out identifying someone who can review this backport. The sig-node team agreed to bump kubernetes with a new hot fix when backport is available.

Thank you!

LGTM, thanks for backporting this.

Thank you! Could you point out to some info regarding the process to cut a new 0.39.x release?

https://github.com/google/cadvisor/blob/master/docs/development/releasing.md describes how to cut cAdvisor releases. This is something that cAdvisor maintainers need to do. I will cut a new release for v0.39 which includes the fix and let you know when it's ready.

pushed https://github.com/google/cadvisor/releases/tag/v0.39.3