airshipctl/manifests/function/airshipctl-base-catalogues
Sirajudeen 00dcad041e Image override for cluster components
* Used images tag to inject image override to clustetctl object,
  the same way the image override is done for cert-manager.
* Using this way, the upstream manifests for cluster components does
  not need any customization (IMAGE URL as variable) and can be consumed as is.
* If this approach is approved, then will update the same for other proviers
  ( CAPO, CAPD, CAPZ, cAPG ) and will get tested.

Change-Id: If920f544d111d94e5b7075d5406ed2f87a5e6929
Closes: #431
2020-12-14 15:27:35 +00:00
..
2020-11-10 12:23:25 -06:00

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.