good question, no it isn’t :(. We are actually using it for Spectro Cloud (Palette). Although our MAAS integration does specify CPU and memory, it doesn’t make sense for us to add disk in the request since we normally target bare metal machines and then we use a CSI configuration to do things like storage. So, adding “disk” to Palette for MAAS would confuse our users as they would normally assume they are using bare metal.
The use case we are seeing though (starting with us) is in labs where container VMs are attractive, and MAAS actually provides a great way to do that, particularly since we use our CAPI provider to get machines from MAAS. It means that labs can be easily spun up/down without even defining machines thanks to the ability of MAAS to create the machines on the fly.
I understand if this doesn’t seem a priority. Even if it were possible to “hack” MAAS to alter the default would be enough to satisfy our use case. I just wondered why the defaults are what they are, and why they aren’t configurable - since 8 GB meant I couldn’t use it out of the box for our usecase.