910d296f6b
Deduplicate networking definitions inside of airshipctl functions, and make the values driveable via a catalogue. Changes: * Removed BMO patches at site level; drive through catalogue instead. * Added separate entrypoints for ephemeral & target site-level. catalogue/networking overrides. Ephemeral's kustomizes target's. * Generalized the commonHostNetworking catalogue into a section in the overall networking catalogue. * Cleaned up catalogue use in general. * Got rid of some ill-formed Type-level phase definition. We should go back soon and define proper Type-level phases. Change-Id: Iff96ccdcf7ebde4ae55e2b1a9d25dd1cdca0d2c8 Relates-To: https://github.com/airshipit/airshipctl/issues/315
1.1 KiB
Function: airshipctl-base-catalogues
This function defines some default VariableCatalogue resources, which can be consumed and used (via ReplacementTransformer) to change the versioning and resource locations used by functions in the airshipctl project. More base catalogues will be added here in the future.
This catalogue can be used as-is to simply apply defaults, or a different
catalogue may be supplied (with the same versions-airshipctl name)
as a kustomize resource. The catalogue in this function can also be
patched at the composite, type, or site level to reconfigure the versions.
The versions info falls under these keys:
-
charts: Helm chart locations and versions
-
files: image file (etc) locations and versions
-
images: container image registries and versions
-
kubernetes: a standalone key for the Kubernetes version to use
Versions that are defined for specific resources in specific functions
(e.g., container images) are categorized in the catalogue according
to the function and resource they will be applied to.
E.g., images.baremetal_operator.ironic.dnsmasq.