https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rke2
a
This message was deleted.
c
set them in the rke2 systemd unit
Copy code
LimitMEMLOCK=
LimitLOCKS=
and so on.
b
you meant in rke2-server unit?
It’s rke2 downstream cluster
c
rke2-server rke2-agent, whatever you have
b
rke2-server what I have. Will try it.
Yep, this works, thanks Brandon!
Well, sort of working. Something is getting restored it back after node reboot. I’m wandering what it could be and how to make it persistent?
c
something is rewriting your systemd unit file?
rke2 doesn’t manage that file, so it would have to be something else
b
I suspect it’s system-upgrade-controller
I had to do it in /etc/systemd/system.conf DefaultLimit* instead of unit file
c
no, that wouldn’t manage it either, that just replaces the binary
If the node was provisioned by Rancher then it would be managed by rancher-system-agent
b
yes, it’s rancher downstream cluster
c
there are many kinds of downstream clusters
not all of them are provisioned by rancher
b
it’s custom, we manage nodes ourselves
c
so you provisioned it via Rancher, as opposed to installing RKE2 manually and then importing it into Rancher
b
yep, create cluster, then install agent via cloud-init. Usual stuff. It’s bare-metal nodes BTW
c
yeah so that is what we could call a Rancher provisioned cluster, and the config is managed by rancher-system-agent
b
yep
206 Views
Open in Slack
PreviousNext
Powered by