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
17 lines
710 B
Markdown
17 lines
710 B
Markdown
Function: ephemeral
|
|
===================
|
|
|
|
This function defines the configuration for a bare metal ephemeral
|
|
bootstrapping image, which can be built via ``airshipctl image build``
|
|
and delivered over the WAN to a remote
|
|
host via redfish using ``airshipctl baremetal remotedirect``.
|
|
|
|
REQUIRED: a ``networking`` VariableCatalogue must 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.
|
|
|
|
Alternately, the entire text payload of the ephemeral secret may be overridden
|
|
via normal Kustomize patching.
|