Files

Sirajudeen 00dcad041e Image override for cluster components

* Used images tag to inject image override to clustetctl object,
  the same way the image override is done for cert-manager.
* Using this way, the upstream manifests for cluster components does
  not need any customization (IMAGE URL as variable) and can be consumed as is.
* If this approach is approved, then will update the same for other proviers
  ( CAPO, CAPD, CAPZ, cAPG ) and will get tested.

Change-Id: If920f544d111d94e5b7075d5406ed2f87a5e6929
Closes: #431

2020-12-14 15:27:35 +00:00

replacements

Image override for cluster components

2020-12-14 15:27:35 +00:00

clusterctl.yaml

Image override for cluster components

2020-12-14 15:27:35 +00: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.