Hi, we made some layout changes to the kubernetes package, which got into the devel:kubic project today and it's on the way to openSUSE Kubic now. What did we change and why? Currently, we use the upstream kubernetes container images for the containerized control plane. But of course, we want to provide our own. Additional, we use currently the fat hyperkube binary. This made sense when we didn't had the containerized control plane, but today, this is only a waste of disk space. E.g., with the changes, we reduced the by kubernetes required disk space by 25%. And if you want to install kubectl on openSUSE Tumbleweed to maintain a remote kubernetes cluster, we are down from 200MB to about 40MB. The second reason is, that this makes building of the required kubernetes container images much easier. If you want to test or use our own control plane already, here is the config file you need for kubeadm with flannel: apiVersion: kubeadm.k8s.io/v1beta1 kind: InitConfiguration --- apiVersion: kubeadm.k8s.io/v1beta1 kind: ClusterConfiguration dns: type: CoreDNS imageRepository: k8s.gcr.io imageTag: 1.2.6 etcd: local: imageRepository: k8s.gcr.io imageTag: 3.3.10 imageRepository: registry.opensuse.org/devel/kubic/containers/container/kubic kubernetesVersion: v1.15.0 networking: podSubnet: 10.244.0.0/16 And yes, coredns and etcd container images will follow the next days ;) Regards, Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org