mirror of
https://github.com/siderolabs/extensions.git
synced 2026-05-05 04:06:38 +02:00
8b18e43f03
Update various dependencies: - gvisor: 20260309.0 -> 20260406.0 - soci-snapshotter: v0.12.1 -> v0.13.0 - kata-containers: 3.27.0 -> 3.28.0 - crun: 1.26 -> 1.27 - qemu-guest-agent: 10.2.1 -> 10.2.2 - tailscale: 1.94.2 -> 1.96.4 - newt: 1.10.2 -> 1.11.0 - netbird: 0.67.2 -> 0.67.4 - nut: 2.8.4 -> 2.8.5 - fuse3: 3.18.1 -> 3.18.2 - util-linux: 2.41.3 -> 2.41.4 - pkgs/tools update Signed-off-by: Mateusz Urbanek <mateusz.urbanek@siderolabs.com> (cherry picked from commit a9a1e7dd9e8c759b365cf8fa0c8bc65be10174f8)
nut-client extension
Installation
Usage
Configure the extension via ExtensionServiceConfig document.
You must replace upsmonHost, upsmonUser and upsmonPasswd to match configuration on your nut server.
See upsd.users man page for details.
On Talos, SHUTDOWNCMD must be /sbin/poweroff.
---
apiVersion: v1alpha1
kind: ExtensionServiceConfig
name: nut-client
configFiles:
- content: |-
MONITOR ${upsmonHost} 1 ${upsmonUser} ${upsmonPass} secondary
SHUTDOWNCMD "/sbin/poweroff"
mountPath: /usr/local/etc/nut/upsmon.conf
Then apply the patch to your node's MachineConfig:
$ talosctl patch mc -p @nut-config.yaml
You will then be able to verify that it is in place with the following command
$ talosctl get extensionserviceconfigs
NODE NAMESPACE TYPE ID VERSION
mynode runtime ExtensionServiceConfig nut-client 1
Testing
Confirm extension service is running:
$ talosctl service ext-nut-client
NODE 192.168.1.1
ID ext-nut-client
STATE Running
HEALTH ?
EVENTS [Running]: Started task ext-nut-client (PID 2263) for container ext-nut-client (59m59s ago)
[Preparing]: Creating service runner (59m59s ago)
[Preparing]: Running pre state (59m59s ago)
[Waiting]: Waiting for service "cri" to be "up" (59m59s ago)
[Waiting]: Waiting for service "cri" to be "up", network (1h0m0s ago)
[Waiting]: Waiting for service "cri" to be registered, network (1h0m1s ago)
[Waiting]: Waiting for service "containerd" to be "up", service "cri" to be registered, network (1h0m2s ago)
[Waiting]: Waiting for service "containerd" to be "up", service "cri" to be "up", network (1h0m3s ago)
Trigger a “Full System Shutdown” on the NUT server:
$ upsmon -c fsd
CAUTION ⚠️ This will power off all connected systems.
All connected upsmon clients should perform a full shutdown and power off.