This message was deleted.

Local is detected as k3s because the detection part is automatic (the version has k3s in it). You can't edit the it through rancher though, because managing a box that contains its own universe is easy to screw up and hard to recover from.

@full-painter-23916 Thanks for the comment. I am sorry for misunderstanding; still trying to wrap my head around best practices when rancher is involved... It's not really made explicitly clear that Rancher cannot manage updates of a local k3s cluster or underlying k3os nodes. For instance there are many github issues which say things like "local cluster edit/upgrade is unsupported on single node docker installs" and therefore implying that local cluster edits may be supported on other cluster types. I guess I am just struggling with the chicken-and-egg problem of trying to run Rancher on a cluster. In such a scenario, would I just need to manage the underlying k3os/k3s cluster manually "outside" of rancher? Are the below images the way the local cluster should appear in the Rancher UI when running on a 3 node k3os/k3s cluster? I guess this also means that editing or manage the local cluster yaml via rancher is no longer possible either, correct?