Looks like the LXD fork is starting to add some new features of its own on top of just catching up with what Canonical is doing.

Most of what Canonical was doing was tying lxd into its ecosystem (maas, juju, snaps). No longer beholden to Mark Shuttleworth’s direction the team is now free to add features actual users care about :) plus I reckon a large part of the expertise left that company, so it seems to me it’s Canonical who will have catching up to do very soon.

Who would use this in a pro use-case.. i.e. for anything work related. Why this over k8s

Kubernetes is great when all your infrastructure is built around it, LXD and now Incus are great for when you have existing infrastructure that needs to keep on working. As in, turning physical systems into containers or VMs, running a local private cloud on your lab hardware, ...

Then when you want to deploy stuff with Kubernetes, you run LXD or Incus on your bare metal, create a bunch of VMs on it and deploy your K8s cluster on that, just as you would in a public cloud, but instead on your own hardware.