Using transactional MicroOS with k3s, rebootmgr and kured?
Hi all, just out of curiosity, has anyone tried running a k3s kubernetes "cluster" on openSUSE MicroOS with transactional updates, rebootmgr and kured to manage the automatic reboots? k3s runs fine on my Raspi4 with MicroOS, but I did not try out whether kured can be deployed and it works with k3s and transactional updates and rebootmgr? Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
On Thu, Jun 10, Johannes Kastl wrote:
Hi all,
just out of curiosity, has anyone tried running a k3s kubernetes "cluster" on openSUSE MicroOS with transactional updates, rebootmgr and kured to manage the automatic reboots?
k3s runs fine on my Raspi4 with MicroOS, but I did not try out whether kured can be deployed and it works with k3s and transactional updates and rebootmgr?
I haven't tried out k3s yet myself, but: if kured is used rebootmgr is not used, kured does reboot the machine itself directly. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg)
Hi Thorsten, On 10.06.21 at 11:53 Thorsten Kukuk wrote:
I haven't tried out k3s yet myself, but: if kured is used rebootmgr is not used, kured does reboot the machine itself directly.
Sorry, my bad, I thought rebootmgr was the one doing the daily transactional updates and then either rebooting or telling kured... I'll test this. Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
On Thu, Jun 10, Johannes Kastl wrote:
Hi Thorsten,
On 10.06.21 at 11:53 Thorsten Kukuk wrote:
I haven't tried out k3s yet myself, but: if kured is used rebootmgr is not used, kured does reboot the machine itself directly.
Sorry, my bad, I thought rebootmgr was the one doing the daily transactional updates and then either rebooting or telling kured...
transactional-update is doing the daily updates, configureable with systemd timers. rebootmgr is not involved in this. transactional-update tells the configured reboot method, to reboot the machine. By default this is rebootmgr, who would reboot the machine in the configured maintenance window. But you can also configure other methods like kured. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg)
On Thu, 2021-06-10 at 11:22 +0200, Johannes Kastl wrote:
Hi all,
just out of curiosity, has anyone tried running a k3s kubernetes "cluster" on openSUSE MicroOS with transactional updates, rebootmgr and kured to manage the automatic reboots?
k3s runs fine on my Raspi4 with MicroOS, but I did not try out whether kured can be deployed and it works with k3s and transactional updates and rebootmgr?
Kind Regards, Johannes
We have a SLE Micro customer effectively doing this, upstream k3s installed atop regular SLE Micro, with kured managing the reboots (as Thorsten has already said, rebootmgr would be redundant in this case). All of this should work on openSUSE MicroOS straight out of the box, with the one exception being the need to disable SELinux, as k3s will try and non-transactionally install invalid packages if it detects SELinux is present by default. Regards, -- Richard Brown Linux Distribution Engineer - Future Technology Team Phone +4991174053-361 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer
On Thu, 2021-06-10 at 13:06 +0200, Richard Brown wrote:
All of this should work on openSUSE MicroOS straight out of the box, with the one exception being the need to disable SELinux, as k3s will try and non-transactionally install invalid packages if it detects SELinux is present by default.
Just a heads up, if you install k3s with the get.k3s.io script you also need to change the SELINUX from enforcing to permissive. otherwise the install script will fail trying to apply container_runtime_exec_t to ${BIN_DIR}/k3s -- Jonas Forsberg SUSE Phone: +46 70 392 10 20 c/o WeWork Malmskillnadsgatan 32 111 51 Stockholm Sweden -- Jonas Forsberg SUSE Phone: +46 70 392 10 20 c/o WeWork Malmskillnadsgatan 32 111 51 Stockholm Sweden
On Thu, 2021-06-10 at 12:37 +0000, Jonas Forsberg wrote:
Just a heads up, if you install k3s with the get.k3s.io script you also need to change the SELINUX from enforcing to permissive.
In the file /etc/selinux/config that is. -- Jonas Forsberg SUSE Phone: +46 70 392 10 20 c/o WeWork Malmskillnadsgatan 32 111 51 Stockholm Sweden
Hi Richard, On 10.06.21 at 13:06 Richard Brown wrote:
We have a SLE Micro customer effectively doing this, upstream k3s installed atop regular SLE Micro, with kured managing the reboots (as Thorsten has already said, rebootmgr would be redundant in this case).
My bad, I mixed up the components. I'll give it a try.
All of this should work on openSUSE MicroOS straight out of the box, with the one exception being the need to disable SELinux, as k3s will try and non-transactionally install invalid packages if it detects SELinux is present by default.
My Raspi4 is on a old enough image to not have SELinux, so I did not run into this issue. But thanks for the heads up. Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
participants (4)
-
Johannes Kastl -
Jonas Forsberg -
Richard Brown -
Thorsten Kukuk