910d296f6b
Deduplicate networking definitions inside of airshipctl functions, and make the values driveable via a catalogue. Changes: * Removed BMO patches at site level; drive through catalogue instead. * Added separate entrypoints for ephemeral & target site-level. catalogue/networking overrides. Ephemeral's kustomizes target's. * Generalized the commonHostNetworking catalogue into a section in the overall networking catalogue. * Cleaned up catalogue use in general. * Got rid of some ill-formed Type-level phase definition. We should go back soon and define proper Type-level phases. Change-Id: Iff96ccdcf7ebde4ae55e2b1a9d25dd1cdca0d2c8 Relates-To: https://github.com/airshipit/airshipctl/issues/315
19 lines
857 B
Markdown
19 lines
857 B
Markdown
Function: k8scontrol
|
|
====================
|
|
|
|
This function defines a KubeADM and Metal3 control plane, including
|
|
Cluster, Metal3Cluster, KubeadmControlPlane, and Metal3MachineTemplate
|
|
resources.
|
|
|
|
Optional: a ``versions-airshipctl`` VariableCatalogue may be used to
|
|
override the default Kubernetes version and controlplane disk image.
|
|
A base example for this catalogue can be found in the ``airshipctl-base-catalogues``
|
|
function. If using the catalogue, apply the ``replacements/`` entrypoint
|
|
at the site level, as a Kubernetes transformer.
|
|
|
|
Optional: a ``networking`` VariableCatalogue may be used to
|
|
override some Kubernetes networking configuration.
|
|
A base example for this catalogue can be found in the ``airshipctl-base-catalogues``
|
|
function. If using the catalogue, apply the ``replacements/`` entrypoint
|
|
at the site level, as a Kustomize transformer.
|