Hi everyone. I'm pretty new to the openSUSE / SUS...
# general
a
Hi everyone. I'm pretty new to the openSUSE / SUSE ecosystem and had to move pretty rapidly to migrate from a competing k8s distribution to rancher. I've got several rancher managed k3s and rke2 clusters with everything running on openSUSE Leap Micro 6.1 at the moment. I have recently discovered the consequences of not having any intentional configurations in place for transactional-update which unfortunately meant every node in a cluster has simultaneously restarted in order to update the operating system 😬 Any best practice approaches to avoid this?
systemctl disable --now transactional-update.timer
seems like a heavy handed tactic... Configuring specific update windows or various delays across the cluster nodes with
systemctl edit transactional-update.timer
seems like an option going in the right direction but was hoping for others with more experience to chime in and possibly point out something I'm missing like a direct integration with k8s of some kind that allows for nodes to be drained first?
w
systemctl disable transactional-update.timer
might seem heavy handed but it's the solution SUSE uses with SUSE Multi-Linux Manager on SUSE Linux Micro