Currently TrueNAS keeps wiping out any changes to e.g. what port Incus should listen to on the network, any DNS zone settings, custom networks and all that.
Incus already has a robust, secure system in place for adding other Incus servers as remotes as long as they have a listening port enabled. Adding a remote would then allow you to copy and move instances between them, allowing for e.g. easy backups or if you are planning to do maintenance on a system, it allows one to move their instances easily from one server to another.
In a similar vein, allowing one to e.g. configure DNS zones for Incus’s networks lets one e.g. point one’s router’s DNS resolver to the server for e.g. ‘.server1.incus’ subdomain, thereby allowing all the devices on the network that use the router’s DNS resolver to resolve the IP address or the hostname of an IP-address running on that Incus network. You could also just simply spin up a new instance and POOF – all the devices on your network can immediately resolve that instance’s IP-address by name!
Why would you want any of this? Well, like I said, allowing one to expose Incus remote management port would make backups easy and everyone loves good backups! And allowing DNS zone settings to be configured would e.g. make it easy to set up a reverse proxy to expose some of your instances’ services to the Internet. Without this, you always have to manually update the reverse proxy settings every time you e.g. move the instance to another server or you’ll have to use MACVLAN, but then the server running the instance can’t communicate with the instance without jumping through extra hoops!