This message was deleted.
# k3da
adamant-kite-43734
09/06/2023, 6:47 PMThis message was deleted.
c
creamy-pencil-82913
09/06/2023, 6:48 PMno, no plans to support provisioning them from Rancher. You should be able to import them into rancher though.
creamy-pencil-82913
09/06/2023, 6:48 PMsame as any other cluster
a
ancient-florist-59155
09/06/2023, 6:49 PMthx, sure importing would work as based on API. Background is to deploy small clusters on top of Devies which have a container runtime, think about the NAS machines etc.
ancient-florist-59155
09/06/2023, 6:49 PMBut, thanks for quick reply
c
creamy-pencil-82913
09/06/2023, 6:50 PMI’m not sure why you’d run a full cluster in k3d as opposed to just using a single-node k3s cluster? In Docker or just standalone as a systemd service.
creamy-pencil-82913
09/06/2023, 6:50 PMIf you’re running it on a single device you’re not getting any true HA out of it, just more overhead
a
ancient-florist-59155
09/06/2023, 6:51 PMYeah, but k3s needs a OS to run, and if you "just" have a Container Runtime availabel?
c
creamy-pencil-82913
09/06/2023, 6:51 PMcontainer runtimes exist on top of an OS as well
creamy-pencil-82913
09/06/2023, 6:51 PMIf you have containerd or docker, you have an OS that could run K3s natively
a
ancient-florist-59155
09/06/2023, 6:52 PMI'm. absultly aware about the HA aspects, the use case is basically this one:
c
creamy-pencil-82913
09/06/2023, 6:54 PMor if you must run it in docker, you could just run the k3s docker image directly; there’s no value add in a multi-node cluster in Docker for production use cases. K3d is great for dev work where you want to simulate multiple nodes for development, but it doesn’t make sense for actual workloads.
☝️ 1
a
ancient-florist-59155
09/06/2023, 6:54 PMYes, this was coming to my mind as well... thanks