Recently i needed to access an inaccessible ipmi on a system running pfsense / freebsd.
Luckily current pfsense releases come with ipmitool shipped. So let's try it:
As you can see, ipmitool is searching for the ipmi device folders, but these are available. The reason for this is because the required kernel driver is not loaded by default (a reasonable decision because the number of use cases is rare). So let's load the module.
Having loaded the module we can access the ipmi.
After having done the required configuration, let's unload the module again.
Always load the module
In case you need to load the module on every boot, you'll need to configure the bootloader by editing /boot/loader.conf and adding the following content:
This configuration is not part of pfsense's config.xml and therefore not included in any config backups / restores.
On a recent project I've been stumbling on the case that kerberos tickets have been inadvertently shared across containers on a node - which obviously caught my attention as I'm not keen on sharing such secrets across workloads. This post describes why this happens and what to do to prevent this.
If you run kubernetes on your own, you need to provide a storage solution with it. We are using ceph (operated through rook). This article gives some short overview about it's benefits and some pro's and con's of it.