This message was deleted.
# rke2
a
This message was deleted.
h
I did this upgrade to
v1.33.7+rke2r3
from
v1.33.7+rke2r1
few days ago but am running on RHEL 9.6 am not seeing this issue... Maybe you want to see what is consuming the resources
Copy code
kubectl top pod -A  --sort-by=cpu
and look at that pod's log and log from rke2-server systemd unit file
Copy code
journalctl -u rke2-server.service
b
I added a matching github issue. Looks like a bug, but only on the first master (where the first etcd is running).
👍 1
Judging from that issue, you should also see that on RHEL. The "parent" issue https://github.com/k3s-io/k3s/issues/13574 is mentioning Rocky too.
c
If a single core in your vm running at 100% usage is enough to make your keyboard laggy, that's probably a problem with your vm.
There are already releases out to fix that btw. They came out Friday so they will be marked prerelease until Monday but they are done and available.
b
Well, since any other RKE2 version is running fine in that VM, it's clearly a RKE2 problem. (Did you see that I also mentioned another Hypervisor? It's from your company and it's also slow, but "elsewhere") Even though Virtual box also has a bad history of nasty issues, they are not to blame this time, IMHO. Thanks for the info about the fix, please make sure, that we will see it in KDM soon!
@creamy-pencil-82913 v1.33.8+rke2r1 is still a pre-release. How come?
c
Because we don't clear pre release on Fridays and Monday was a US holiday and most of the team is US based.
Forgot about the upcoming holiday when I commented last week
👍 1
Poking me about it here will not speed things up, it'll be done when release and QA teams complete their work.
b
I just wanted to know a date... our users keep asking me the same. So take your time, but not too long.
It's released. Great. Now waiting for the KDM 🙂