This message was deleted.

Rancher does a lot of things but it depends on what exactly you want... this page gives you good explanation https://ranchermanager.docs.rancher.com/

hi @hundreds-evening-84071 will take a look at that page..

you should also keep this support matrix handy... https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-10-1/

So I just really want to deploy the web interface management, and have it connect to my running k3s... question is, is that normal deploy, and correct?

yeah so k3s was originally started by Rancher labs but as you know now SuSE acquired Rancher and yes some things are still spread out

sounds pretty spread out 😄

Miles, you can do it quickly if you read the docs. It sounds like you are running this for your lab, three options below. 1. Run rancher as a container in a vm and then import your k3s cluster into it. (great for testing , not for prod) Docs 2. Run a single vm and install k3s or rke2 and then install rancher using helm. (great for testing, not for prod) Doc 3. Install rancher on your current cluster, same doc as 2 Optional: you can build a vm with rancher first and then create the k3s cluster from rancher and install it to a blank debian vm to make a managed cluster with just an install script. It has more integration doing it this way than an imported cluster.

hi @mysterious-animal-29850 thank you for that info. Will try these out

sounds good, good luck.

its so vast, I'm quite taken aback 🙂