ARM versions available ?

[nlamirault]

Do you know if ARM images exist ?
I try that but it fails :

$ docker pull gcr.io/heptio-images/sonobuoy-arm:v0.10.0
Error response from daemon: manifest for gcr.io/heptio-images/sonobuoy-arm:v0.10.0 not found

[chuckha]

Ah, we do not support ARM at this time.

[vielmetti]

@chuckha @nlamirault - or anyone who wants to make a go at this - if you need Arm gear for a build/test cycle, Packet and Arm run a "Works on Arm" cluster at http://worksonarm.com/cluster . Submit a proposal at http://github.com/worksonarm/cluster/issues for access.

[vielmetti]

I suspect that the right path once there's Arm support is to offer up a "fat manifest" with multiplatform support. Pinging @tianon who has always had good suggestions for build changes that would make this happen.

[liztio]

The sonobuoy image doesn't actually execute all of the tests. We run the kubernetes E2E tests, and they require a lot of their own images. It'd be a lot of work to get all of those arm-capable, so this would be far from trivial.

[luxas]

@liztio These are already cross-built and working on multiple platforms... The only thing needed is to make the images on your side cross-built and manifest lists, which should be an ok-sized task to do.

LMK if you need guidance how to do so :)

[timothysc]

I'd like us to sort out how we plan to publish new artifacts 1st.

[timothysc]

@nrb let me know if/when our new tooling can do some of this and I will enable this.

[nrb]

@timothysc Sorry, I think I'm missing something - which part? Publishing artifacts?

[hh]

@luxas @timothysc have we come up with a consensus on how to publish artifacts?
I'd know there is interested see if we quickly we can get our first Certified Kubernetes on ARM provider.
What are we missing at this point?

[timothysc]

@hh the biggest issue is getting all the upstream test containers pushed for every arch.

that + pull-images option.