Create tool to make airgapped easier

[richardcase]

A common scenario for our customers is running Rancher in an air-gapped environment.

For CAPI this would require the use of:

• provider/core manifests packages as config maps
• Images from an internal registry

Currently this is a very manual process and so we can to create some tooling (i.e. a CLI) that will make this easier.

Todo:

• [CLI] Scaffold cli utility #365
• [CLI] Add ability to package core/providers as CM #366
• [CLI] Support republishing CAPI images #367

[richardcase]

We need to look at Hauler used by RGS:

https://github.com/rancherfederal/hauler

[alexander-demicev]

Images part can be solved with hauler and packaging CAPI operator providers through the upstream CAPI operator plugin

[hardys]

@alexander-demicev can this perhaps be reopened, as IMO it's not completely resolved yet

If you check the discussion on suse-edge/charts#154 you can see that we still need a way to make management of the provider ConfigMaps easier, for now I created a chart to handle that for the edge use-case, but in future it would be better to have a solution provided via Turtles directly IMO.

I like the suggestion made by @Danil-Grigorev that we could package the provider ConfigMaps inside a container image (to work around the helm size limit issue), this could be applied via a pre-install hook perhaps or even be supported directly in the CAPI operator perhaps (optional initContainer which loads the ConfigMaps?)

[alexander-demicev]

@hardys Sounds reasonable, I will reopen the issue

[alexander-demicev]

Closing in favor of #968