This message was deleted.
# rke2
a
This message was deleted.
r
The answer I got about that a year or three ago from a Rancher person is that as soon as a node detects something it pushes it, so you only need to put it in one. If they conflict in an HA env, whichever one was noticed last will be what was deployed.
c
See the caution in the User AddOns section:
If you have multiple server nodes, and place additional AddOn manifests on more than one server, it is your responsibility to ensure that files stay in sync across those nodes. K3s does not sync AddOn content between nodes, and cannot guarantee correct behavior if different servers attempt to deploy conflicting manifests.
s
Ah, I didn't think to look in the k3s docs. Thanks!
c
We try to keep them roughly parallel, but the K3s docs usually get updated first, and then the updates eventually make their way over to RKE2.
👀 1
for things that are the same in both, at least
s
Good to know! It's very hard to keep good docs, especially when there needs to be multiple sites.