Comment 1 for bug 1407718

I think curtin is pretty stable and placing a hook in the image itself (/curtin/curtin-hooks) is a reasonable approach, not much of a chance of curtin changes affecting us.

curtinator could do this directly on the received tarball, we have more flexibility and control than what can be achieved in the preseed.

I hadn't noticed this behavior since at the moment, all I've been doing is ensuring that the system boots correctly after maas provisioning; but for our use case, we also want to boot with the image's own kernel, for certification purposes (although for certification we mostly care about the latest point release so it may not be such a big issue for us).