airship/airshipctl
Code Issues Proposed changes
f9411f40f7
airshipctl/manifests/function/airshipctl-base-catalogues
History
Zuul 0c36a47ee3 Merge "adding installation registry to version catalogue"
2021-07-16 17:16:13 +00:00
..
env-vars-template.yaml Externalize KRM function versions 2021-05-26 20:18:49 +00:00
kustomization.yaml Deduplicate airshipctl manifest networking 2020-10-21 16:26:10 -05:00
networking.yaml Add ntp to network catalogue 2021-05-19 15:13:34 +00:00
README.md Define structural schema for VersionsCatalogue 2021-02-24 18:00:28 +00:00
versions-airshipctl.yaml Merge "adding installation registry to version catalogue" 2021-07-16 17:16:13 +00:00

README.md

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:

  • helm_repositories: Helm chart locations

  • charts: Helm chart names and versions

  • files: image file (etc) locations and versions

  • capi_images: cluster-api container image registries 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.