airship/airshipctl
Code Issues Proposed changes
d2da9c3d4c
airshipctl/manifests/function/clusterctl
History
Sreejith Punnapuzha 2db7d3d85c move ipam from url to local 
ipam yaml was getting downloaded in customization file. This will cause
problem behind proxy. So adding the ipam yaml to respective folder

Signed-off-by: Sreejith Punnapuzha <Sreejith.Punnapuzha@outlook.com>
Change-Id: Idf0f4b13fb6380363d3cabacfeacc7179f09cff9
2021-03-12 17:00:06 -06:00
..
replacements move ipam from url to local 2021-03-12 17:00:06 -06:00
clusterctl.yaml move ipam from url to local 2021-03-12 17:00:06 -06:00
kustomization.yaml Add catalogue-driven CAPI container versions 2020-09-14 18:01:06 +00:00
README.md Deduplicate airshipctl manifest networking 2020-10-21 16:26:10 -05:00

README.md

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-base-catalogues function for a base/example.