I'm not totally sure why the thick image is different from the thin one here, but it doesn't seem like there should be anything stopping the thick image from being multiarch.
coverage: 63.116%. remained the same
when pulling 572e4e05e34ba2b134144cc1fc1dfb80cafe63d9 on sfackler:thick-arm
into aff99fccc5fe3b21aec84bb56a6d1bbaf8ffc45b on k8snetworkplumbingwg:master.
I'm not totally sure why the thick image is different from the thin one here, but it doesn't seem like there should be anything stopping the thick image from being multiarch.