Closed SteffenBlake closed 2 years ago
Looks like this is an upstream issue: https://github.com/kubernetes/kubernetes/issues/95039
Perhaps fixed in 1.21.
@SteffenBlake can you try https://github.com/rancher/k3os/releases/tag/v0.21.1-k3s1r0 and see if the issue persists?
@dweomer issue seems to be resolved, though a new log message error shows up (seems unrelated), however Ill open a new issue for that one if you prefer.
@dweomer issue seems to be resolved, though a new log message error shows up (seems unrelated), however Ill open a new issue for that one if you prefer.
please do
Version (k3OS / kernel)
k3os --version
: v0.19.11-k3s1r0uname --kernel-release --kernel-version
: 5.10.60-v8+ #1449 SMP PREEMPT Wed Aug 25 15:01:33 BST 2021Architecture
uname --machine
: aarch64CPU
lscpu
output:Describe the bug Every few minutes, the following logs show up in
/var/log/k3s-service.log
To Reproduce Get the image via my fork of the following repo: https://github.com/SteffenBlake/picl-k3os-image-generator
You will need the mac address of your raspberry pi as well, as per the instructions, and a working yaml cloud config file.
Copy your cloud config to said yaml file, then:
Then copy/burn/etc the image which will be now located at
/temp/picl-k3os-image-generator/picl-k3os-v0.19.11-k3s1r0-raspberrypi.img
On boot you should see the logs show up shortly on the raspberry pi device.
Expected behavior Im not sure how much these logs inherently matter, but I also have non raspberry pi devices on my cluster which dont have this issue, and I have noticed all deployments/pods/statefulsets/etc, if given the option, will always choose the non raspberry pi machines over the raspberry pis, no matter how much is already on them.
This has resulted in even with several deployments my raspberry pis still only have daemonsets running on them, since it is forced.
Additional context Current config yamls of all my agent devices that are raspberry pis: