Comment 12 for bug 1896630

Would you want to put every instance in your large scale infrastructure in the same namespace/subdomain? Probably not. Do the public clouds provide your instance with a FQDN? They do. Do you want to rely on IP addresses only to have to change everything in case of IP renumbering? Absolutely not.

This is a generic on-metal problem, and it won't go away regardless of what Juju is putting on metal.

If you want to detect and tackle situations where LXD containers come up without networking in a different way that would also work for us. But providing the instance with the data it needs is a solid and durable fix, and there is a reason for MAAS putting the FQDN in /etc/hosts on the physical machine.

While the desire to treat all the provider drivers equally is noble, they are quite different already, and do you really want to dilute Juju's on-metal capabilities with a least common denominator approach?

Would forwarding FQDN to cloud-init user-data when we know the provider manages it be possible?

The making cloud-init use it part could be up to the charm author to set through a lxd-profile so that you don't risk a change of default behavior situation.