Hi, Am Mittwoch, 28. August 2019, 08:23:50 CEST schrieb Thorsten Kukuk:
Hi,
On Sun, Aug 25, Michal Rostecki wrote:
And indeed, it seems that kube-proxy image is available only for x86_64. [1] I have no idea why - in the devel project it seems do build fine for container_ARM.[2]
In Factory, too: https://build.opensuse.org/package/show/openSUSE:Factory:ARM/kubic-kube-prox...
Do you have any ideas why OBS does not build the kube-proxy image for aarch64 and how we can fix that?
Dominique, is the kubic-kube-proxy-image missing in the list of images to be pushed to r.o.o?
IIRC kube-proxy didn't build for a while and so was not enabled. That got fixed a few days ago already (note that the mail is from Sunday) and the next TW ARM snapshot will have it. That might take a day or more. FYI, the list of to-be-published images can be found in the ToTestManagerConfig attribute on https://build.opensuse.org/attribs/openSUSE:Factory:ARM Cheers, Fabian
Michal, you can use the kubeadm option and point it to the kubic:devel project in the registry until we get the missing container out.
Thorsten
Cheers, Michal
[0] One of the reasons is that I want to have a working environment for testing Cilium as soon as I'm finally done with all the madness with Bazel and making Envoy work on aarch64 ;) [1] registry.opensuse.org and look for '^kubic/kube-proxy' [2] https://build.opensuse.org/package/show/devel:kubic:containers/kubic-kube-pr...
-- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org