Add-ons Specified in Manifest Are Not Installing

[JeremyEstradaEupraxia]

For your manifest templates within kind: MicroK8sControlPlane -> spec.controlPlaneConfig.initConfiguration.addons, I believe I am specifying the values correctly for certain add-ons listed from this documentation page. However, a vast majority of the add-ons I seem to insert as values within the manifest do not seem to be installing correctly or at all (with the exception of the ones specified in the samples). Even when you run microk8s enable <addon-name> on the master node, there does seem to be the need of human interaction due to pre-requisite requirements. For example, Mayastor will need HugePages enabled for the installation.

Therefore, is there any way to add the capability of running a string array of custom commands inside of the CAPI manifest prior and after MicroK8s is installed in the initial control plane node? This will ensure certain add-ons can work and be properly installed directly from the CAPI manifest, preventing any other sort of human interaction generally done now in the initial master node.