Skip to content

Linux

Patching and Upgrading SLE Micro from Rancher

When you upgrade OpenShift , the operating system comes along. CoreOS and the cluster move together, node by node.

The Rancher ecosystem, including K3s and RKE2 , leaves the choice and management of the OS completely open.

My recommendation is to use an immutable distribution. In my customer projects, that is most of the time SLE Micro .

The lifecycle is therefore split in two : Kubernetes upgrades on one side, OS upgrades underneath on the other. Rancher gives all the tools to manage both from a single stack.

I drive SLE Micro's lifecycle from Rancher, the same way we drive Kubernetes. Everything runs on a live cluster while an application keeps answering.

Installing SUSE Linux Micro on Hyper-V

SUSE Linux Micro doesn't install like regular desktop or server OS ; farewell the YaST wizard.

The selfinstall ISO just copies a pre-built image to disk, then runs a first-boot configuration from a labeled block device you provide.

The official documentation was both too long for my usage and too shallow with regards to Hyper-V.

Here's the shortest path from zero to a running SLE Micro on Hyper-V.

Here is the video walkthrough in one take & realtime :

🔒🧰 Hardening Kubernetes CSI Drivers: Reducing CAP_SYS_ADMIN Without Breaking Storage

Many Kubernetes storage drivers still rely on the powerful—and notoriously over‑broad—Linux capability CAP_SYS_ADMIN to perform host‑level operations. While it enables critical actions like filesystem mounts, it also substantially expands the attack surface of your cluster.

This post explains why CSI node plugins often end up needing CAP_SYS_ADMIN, what breaks when you remove it, and several concrete hardening strategies using tools like seccomp, AppArmor, SELinux, and controlled privilege elevation.