airship/airshipctl
Code Issues Proposed changes
0f287089d9
airshipctl/manifests/function/airshipctl-base-catalogues
History
Sirajudeen 909d427610 Container build for Templater plugin 
Change-Id: I53384561517070a0dca901ee263a5c1a1e55dffa
Relates-To: #341
2020-10-22 00:07:24 +00:00
..
env-vars-template.yaml Container build for Templater plugin 2020-10-22 00:07:24 +00:00
kustomization.yaml Deduplicate airshipctl manifest networking 2020-10-21 16:26:10 -05:00
networking.yaml Deduplicate airshipctl manifest networking 2020-10-21 16:26:10 -05:00
README.md Deduplicate airshipctl manifest networking 2020-10-21 16:26:10 -05:00
versions-airshipctl.yaml Deduplicate airshipctl manifest networking 2020-10-21 16:26:10 -05: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:

  • 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.