are we supposed to use ansible with rke2 in HA mod...
# rke2
w
are we supposed to use ansible with rke2 in HA mode(multiple servers)? What happens with the add-on configurations as helm variables. Do we have to set them on all server nodes or only on the first one?
c
Supposed to? You certainly can but I would not say that you are supposed to. We don't document that anywhere and we do not use ansible ourselves.
w
yes, or some similar tool. The point is that rke1 cli had a different approach to distribute the configuration state itself on the nodes. Also can you elaborate on the second question? In the documentation we are supposed to configure the addons via the
/var/lib/rancher/rke2/server/manifests/
files Are they ignored on the other nodes? or we have to be sure to propagate all the changes to all server nodes?
Copy code
Any Kubernetes manifests found in /var/lib/rancher/rke2/server/manifests will automatically be deployed to RKE2 in a manner similar to kubectl apply, both on startup and when the file is changed on disk
If I join a new server node with the default files, it would revert any changes?
c
> Deleting files out of this directory will not delete the corresponding resources from the cluster. If the file doesn’t exist, nothing happens. The resource is left in the same state as last defined in the file. Same is true regardless of whether file does not exist because you didn’t place it on that node, or because you deleted it.
w
yes, but there are default files
c
you are not to modify those. The docs page also covers this. > Manifests for packaged components are managed by RKE2, and should not be altered. The files are re-written to disk whenever RKE2 is started, in order to ensure their integrity.
Did you stop reading at the first sentence?
w
yes, I did not read the "customize" part, as I thought it was referring to custom add-ons 🙂 thank you for the help