zarf init package manifest creation

[brandtkeller]

Would like to test the full airgap experience by replacing the k3s component of a standard zarf init package with a mk8s component.

This makes the assumption that each init package currently would need to be built by the deployer with information about the nodes before creation.

Need to evaluate in the future how to make this more configurable.

[TheFutonEng]

@brandtkeller , this is a worthwhile target to shoot for but probably a massive issue in terms of effort. Guessing this is here more as a placeholder for when mk8s is a little further along?

[brandtkeller]

@TheFutonEng I'd agree on it being a placeholder - but may work on an initial prototype to understand architectural decisions about how to effectively provide configuration options.

IE right now I don't know how we could create a configurable init-package with mk8s included. Due to all the node configuration required you really need to either:
a. Have each environment build the mk8s init package themselves
b. support for imperative runtimes (IE allow for dropping all required information into a CLI command - it would be LONG but certainly possible.

Or some other option? maybe something in Zarf now or in the future could support inclusion of a manifest-like file during zarf init for a specific component?