Hello, I am currently trying to generate a Chef co...
# general
b
Hello, I am currently trying to generate a Chef cookbook for rke2-agent and rke2-server configuration using the RPM install method. When I try to install the rancher-system-agent it complains about the rpm managing the install and wants to use a Tarball and it asks me to uninstall the RPM before continuing. Im curious if anybody has a Chef cookbook they have created or some other options for automating the deployment of rke2-agent and rke2-server? Are their advantages to using the Tarball over RPM?
b
RPM allows for SELinux policies, Tar allows for offline installs.
It also manages configurations that are necessary to get things working on different OS
b
Thanks! I'lll have to give this a shot.
c
If you are using Rancher to deploy rke2 you must allow rancher-system-agent to install and manage rke2. You must not use your own tooling to manage the install. Rancher-system-agent only supports tarball, so that is what you will have.
b
Oh, yeah ^^this if you are using Rancher
b
Thanks guys. We will be purchasing Rancher Prime in the near future. Do you happen to know the recommended installation method for connecting agents and servers to a Rancher Prime managed cluster? We would like to be able to automatically connect servers and agents and assume it would be similar to the Open Source version of Rancher, but not sure.
c
If you are installing and configuring RKE2 yourself, you do not connect individual nodes up to Rancher. You connect the cluster to Rancher.
If you are provisioning the nodes and configuring RKE2 by hand, and then importing the cluster into Rancher, then there is no rancher-system-agent or node-level management through Rancher. If you are using Rancher to provision clusters, then it manages the nodes and rke2 configuration via rancher-system-agent.
This is not unique to Prime or Community, they both work the exact same way…
If you’re using Rancher custom cluster provisioning, all you do is run the rancher-system-agent install script. You need to be 100% hands-off after that, and manage all the cluster and rke2 node config through Rancher.