airshipctl/manifests/function/clusterctl
Ruslan Aliev d8a6139e81 Add document pull step to gate script runner
Currently we don't test document pull step by rewriting
manifest_directory variable as current source path, which
makes a mess in target_path, manifest_path and related paths
(concatenation of target_path+manifest_path won't return
an existing and proper location). This patch organizes
mentioned variables and enables document pull step which
starts working properly. The latest repo state used as
git source for this command.

Change-Id: I5abce73877441c7529f2f77add79cf410e2226d8
Signed-off-by: Ruslan Aliev <raliev@mirantis.com>
2020-09-25 00:39:28 -05:00
..
replacements Add catalogue-driven CAPI container versions 2020-09-14 18:01:06 +00:00
clusterctl.yaml Add document pull step to gate script runner 2020-09-25 00:39:28 -05:00
kustomization.yaml Add catalogue-driven CAPI container versions 2020-09-14 18:01:06 +00:00
README.md Add catalogue-driven CAPI container versions 2020-09-14 18:01:06 +00:00

Function: k8scontrol

This function defines a base Clusterctl config that includes a collection of available CAPI providers (under providers) which are supported by airshipctl. It also provides a selection of those for a default Metal3 deployment (under init-options). The selected init-options may be patched/overridden at the Type level, etc.

This function relies on CAPI variable substitution to supply versioned container images to the CAPI components. The Clusterctl objects supplies defaults, and these can (optionally) be overridden either by simple Kustomize patching, or by applying the replacements kustomization as a Kustomize transformer. In the latter case, an airshipctl versions catalogue must be supplied; please see the airshipctl-catalogues function for a base/example.