Build google/cadvisor:latest for multi architecture

[mkumatag]

What happened:
Following 3 node tests got a prereq of google/cadvisor:latest which is not yet multi-architectured. This issue is to track the work for making this image multi-arch manifest.

[Fail] [sig-node] Resource-usage [Serial] [Slow] regular resource usage tracking [It] resource tracking for 10 pods per node
_output/local/go/src/k8s.io/kubernetes/test/e2e_node/resource_usage_test.go:192

[Fail] [k8s.io] Density [Serial] [Slow] create a batch of pods [It] latency/resource should be within limit when create 10 pods with 0s interval
_output/local/go/src/k8s.io/kubernetes/test/e2e_node/resource_usage_test.go:192

[Fail] [k8s.io] Density [Serial] [Slow] create a sequence of pods [It] latency/resource should be within limit when create 10 pods with 50 background pods
_output/local/go/src/k8s.io/kubernetes/test/e2e_node/resource_usage_test.go:192

[mkumatag]

/kind feature
/assign
/sig node

[mkumatag]

I see some discussion about building cadvisor in arm in google/cadvisor#1236 but I don't see any further progress on it. @luxas are you aware of anyone try building this on non-amd64 platform?

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[mkumatag]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[mkumatag]

/remove-lifecycle rotten

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[mkumatag]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.