This message was deleted.
# cabpr
a
This message was deleted.
r
Are you talking about the RKE2 binary, the images or both?
As a general principal CAPI node images have bootstrapping dependencies baked in.
Commands can be run in
preRKE2Commands
.
@creamy-wolf-46823 could you create an issue for this?
c
I'm referring to how the v2 provisioner uses the rancher-system-agent with the following plan to dynamically install any version of rke2: https://github.com/rancher/system-agent/blob/main/examples/install-rke2/install-rke2.plan.
I would expect capbr to offer ease-of-use features like this to justify using it instead of using the mainstream kubeadm bootstrap provider.
r
We could easily add a quality of life API change to install the RKE2 binary.
CAPBR is deliberately more lightweight than the v2 provisioner, and there is no requirement for Rancher (or related components like the system agent).
We're happy to consider any ease-of-use features that are suggested.....so any suggestion you have it would be great to capture them in an issue: https://github.com/rancher-sandbox/cluster-api-provider-rke2/issues/new/choose
👍 1
b
Hi @rapid-van-91305, any way cabpr could optionally be configured to directly use the RKE2 versioned container images already being published here: docker.io/rancher/system-agent-installer-rke2 that embed the necessary RKE2 versioned install artifacts described here: https://github.com/rancher/system-agent-installer-rke2/blob/2fda2b4b6d8553ebfed329c72ad0f85174d7b9a2/scripts/download#L13-L23?
I'm happy to open a cabpr issue if you think such a feature is viable.
r
Thats certainly viable 👍 And it would make it easier to use.
I'd love to hear about any other usability improvements like this
b
I went ahead and opened cabpr issue https://github.com/rancher-sandbox/cluster-api-provider-rke2/issues/220 per your suggestion. I think lots of users migrating to CABPR from the Rancher v2 provisioner would appreciate being able to reuse their existing node images rather than being forced to change their node image build process in order to adopt CABPR. Also, this seems like a nice CABPR ease-of-use value-add over the kubeadm bootstrap provider.