Hello All, I've been watching <https://github.com/...
# harvester
l
Hello All, I've been watching [FEATURE] Baremetal container workload support GA · Issue #5820 · harvester/harvester , however it seems to be blocked now due to a change from vcluster to k3k, however I wouldn't think that has anything to do with baremetal container workloads going GA? Completely different implementations/issues? Just trying to understand when this can be expected to be supported thats all.
👍 1
g
there is nothing stopping you from running baremetal workloads
glitch crab 1
just the last piece of puzzle is blocked due to an issue in rancher + k3k integration
l
Yep totally get that, its just the feature name(bare metal), vs k3k which is virtual clusters, which are not the same even in the docs Rancher Integration | Harvester versus Rancher Manager (Experimental) | Harvester I was looking at when the baremetal side would be supported as GA. Not looking at the vcluster side in my particular instance.
g
the plan for k3k was that users needed crd's that may conflict with harvesters can run those workloads in shared k3k clusters
as the workload will run on underlying baremetal but use a different api server so there is no crd conflicts or impacts to upgrades etc
l
Ah i see. thanks no worries i will be patient 😉