Bump k3s-root for buildroot security updates

[brandond]

k3s-root v0.14.1 updates buildroot from 2024.02.3 -> 2024.02.7 for security updates: https://gitlab.com/buildroot.org/buildroot/-/blob/2024.02.7/CHANGES

We should update k3s-root across all active branches.

To verify, check the k3s packaged busybox build date:

old:

root@k3s-server-1:/# /var/lib/rancher/k3s/data/current/bin/busybox
BusyBox v1.36.1 (2024-07-09 19:18:00 UTC) multi-call binary.

new:

root@k3s-server-1:/# /var/lib/rancher/k3s/data/current/bin/busybox
BusyBox v1.36.1 (2024-11-08 20:32:42 UTC) multi-call binary.

[endawkins]

Validated on branch master with commit 62caa4a / version v1.31

Environment Details

Infrastructure

• Cloud
• Hosted

Node(s) CPU architecture, OS, and Version:

Linux ip-172-31-14-71 5.14.21-150500.55.44-default #1 SMP PREEMPT_DYNAMIC Mon Jan 15 10:03:40 UTC 2024 (cc7d8b6) x86_64 x86_64 x86_64 GNU/Linux
NAME="SLES"
VERSION="15-SP5"
VERSION_ID="15.5"
PRETTY_NAME="SUSE Linux Enterprise Server 15 SP5"
ID="sles"
ID_LIKE="suse"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles:15:sp5"
DOCUMENTATION_URL="https://documentation.suse.com/"

Cluster Configuration:

N/A - configuration does not matter

Config.yaml:

N/A

Additional files

N/A

Testing Steps

1. Copy config.yaml

$ sudo mkdir -p /etc/rancher/k3s && sudo cp config.yaml /etc/rancher/k3s

2. Install k3s
3. /var/lib/rancher/k3s/data/current/bin/busybox

Replication Results:

• k3s version used for replication:

$ k3s -v
k3s version v1.31.2+k3s1 (6da20424)
go version go1.22.8

$ /var/lib/rancher/k3s/data/current/bin/busybox
BusyBox v1.36.1 (2024-07-09 19:18:00 UTC) multi-call binary.

Validation Results:

• k3s version used for validation:

$ k3s -v
k3s version v1.31.2+k3s-62caa4a8 (62caa4a8)
go version go1.22.8

$ /var/lib/rancher/k3s/data/current/bin/busybox
BusyBox v1.36.1 (2024-11-08 20:32:42 UTC) multi-call binary.

Additional context / logs:

N/A

[mdrahman-suse]

Reopening as it should be closed after backports are validated @endawkins