Have a few questions around possible deployment options ... a) Can one effectively do a multi-arch cluster deployment, say some x86_64 and some aarch64 nodes? - this might be relevant mostly to have designated (labeled) worker nodes of the respective variety for targeted workloads b) Parallel to above, would it be possible, given the kubeadm-based approach to include a worker node based on another Linux (with Kubernetes installed) distribution? - as above, this might enable usage of other enabled devices like Jetson/RPi4 which don't yet have openSUSE images available c) From the https://en.opensuse.org/Kubic:kubeadm wiki page, it cites being able to have a single master node (and untaint to allow workload scheduling there). For edge computing (aka gateways), this might be a quite valid usage scenario. Other than potential resource conflicts of such a single node "cluster", any other considerations/caveats? And a couple of issues ... 1) on the same wiki page cited above, for Cilium it cites using /usr/share/k8s-yaml/cilium/cilium.yaml but the file currently residing there is /usr/share/k8s-yaml/cilium/quick-install.yaml. Is this the correct one to now use? 2) for some reason, all of the nodes in a recent deployed cluster show Status = NotReady (which may be related to previously listed issue and my assumption to use the file in that directory), since kubectl describe node <name> shows an error ... "Missing CNI default network" Thanks for any help / guidance -- To unsubscribe, e-mail: opensuse-kubic+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kubic+owner(a)opensuse.org