Dan Sabath

I am also having issues with this. My configuration is as follows. service.yaml ``` ... spec: externalTrafficPolicy: Cluster ports: - name: http nodePort: 30183 port: 80 protocol: TCP targetPort: svc-port...

@SaxyPandaBear, thanks for the quick reply. This is actively breaking our metrics collection so I need to find a work around. Building our own image is not out of the...

@SaxyPandaBear, i've forked the repository and upgraded cadvisor to 0.44.0. It was also necessary to make a small change in cadvisor/container_info_processor.go [to remove the docker scope](https://github.com/kiyose/amazon-cloudwatch-agent/pull/1/files#diff-599185154c116b295172b56311729990d20672f6659500870997c018ce072100R164-R171) and allow look up...

@SaxyPandaBear It looks like there may still be an issue with the metrics being collected. I don't see the code to account for the pod infoname. See[ line 164 of...

@SaxyPandaBear, wanted to see if you have had a chance to take a look. Thanks!

@SaxyPandaBear, I believe that's it. W/o addressing this you aren't able to look up `podKeys` by `info.name` ``` func stripDockerScopeFromContainerInfoName(name string) string { // Hack to remove trailing extraneous information...

Thanks for the quick response. If the recommended installation method on Mac is to not use `brew` then the instructions on this page need to be removed. https://github.com/flatcar-linux/container-linux-config-transpiler#macos-homebrew

@SaxyPandaBear Bumping this to see if anyone has had a chance to review. This is blocking an upgrade for us.

@SaxyPandaBear We have updated to the latest version and we are no longer seeing the issue. I'm closing this issue.

This would be very handy for own environment but the PR hasn't been updated recently. What is the status of this? Thank you