[opensuse-kubic] kube-proxy image missing for aarch64
Hi, I'm trying to set up the RPi cluster with Kubic[0] and I'm getting the following error: kubic-master-1:~ # kubeadm init [init] Using Kubernetes version: v1.15.2 [preflight] Running pre-flight checks [preflight] Pulling images required for setting up a Kubernetes cluster [preflight] This might take a minute or two, depending on the speed of your internet connection [preflight] You can also perform this action in beforehand using 'kubeadm config images pull' error execution phase preflight: [preflight] Some fatal errors occurred: [ERROR ImagePull]: failed to pull image registry.opensuse.org/kubic/kube-proxy:v1.15.2: output: time="2019-08-25T01:23:57Z" level=fatal msg="pulling image failed: rpc error: code = Unknown desc = no image found in manifest list for architecture arm64, OS linux" , error: exit status 1 [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` 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] Do you have any ideas why OBS does not build the kube-proxy image for aarch64 and how we can fix that? 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
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? 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
-- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 247165, AG München) -- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org
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
On Wed, Aug 28, 2019 at 08:52:10AM +0200, Fabian Vogt wrote:
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.
Cool! Thanks for handling that.
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.
Will do. -- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org
participants (4)
-
Fabian Vogt -
Michal Rostecki -
Michal Rostecki -
Thorsten Kukuk