airship/airshipctl
Code Issues Proposed changes
8dddae9daa
airshipctl/manifests/function/airshipctl-base-catalogues
History
Snehal a20eb0b4ba Integrate CAPD 
* Below manifests integrates capd to v1alpha4

* Cluster templates updated to v1alpha4

Closes: #647

Change-Id: I53f25cb2dd1eeed901d8582ddb873f0894bc45b9
2021-11-08 12:02:52 +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 Integrate capi v0.4.2 and capm3 v0.5.0 2021-10-13 13:30:52 -05:00
README.md Define structural schema for VersionsCatalogue 2021-02-24 18:00:28 +00:00
versions-airshipctl.yaml Integrate CAPD 2021-11-08 12:02:52 +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.