This commit allows to stop using phases with hardcoded paths to
kustomize entrypoints. Instead we use phase documents defined
in bundles. Phase document has a reference to executor such as
kubernetes apply and clusterctl init. More executors are being
developed
Relates-To: #342
Change-Id: I8babd9d0379763773c443e263373e9816f9dbd39
* Inject target-cluster-ca as sceret
* Create kubeconfig using gate scripts with both ephemeral and
target clusters.
* With both contexts predefined in kubeconfig,
just switch/use context in gate scripts as required.
* Removed the use of airshipctl import from gate script
Change-Id: I5a9a56db71f0a80d9b35144eacbdd980c13c9ffb
Relates-To: #329
Closes: #329
This adds a verbose guide for example hardwareprofile
highlighting the RAID and firmware configurations that are
currently the features present in it.
Change-Id: I65c23cca60ac57fe152556c7a45eb33c17260b6d
Closes: #338
* add steps to clean iso and network for gates
Change-Id: I7ffc62cac9690e524c559af554ff6d1a70683368
Signed-off-by: Sreejith Punnapuzha <Sreejith.Punnapuzha@outlook.com>
testutil.InitConfig writes sample configs to files,
and if we just check that these files exist after
calling PersistConfig function, then don't test anything.
We have to change config file paths before calling PersistConfig
and then we can check if these files exist.
Change-Id: Ibaee17a57a86251f7016bb57b2d8bd9976cefac0
This change adds the ability to use substring substitution to inject
numeric source values into string targets. This is required for our
networking catalogue, since a numeric k8s API port needs to be inserted into
numeric and (sub)string targets in different phases.
Co-Authored-By: Ian Howell <ian.howell0@gmail.com>
Change-Id: I24beb46a2bda4e118406129a0a922b0c56142c76
* uplift capi, cabpk, cacpk and capm3 in test site defination
* uplift images in version catalogue
* add api timeout in controlplane
* add timeout for phases
Change-Id: I9de15c4e1979c12eeedb55fbe721b5e7adfe496b
Signed-off-by: Sreejith Punnapuzha <sreejith.punnapuzha@outlook.com>
This allows for container locations and versions for the CAPI functions
to be (optionally) driven by the `versions-airshipctl` versions
catalogue. In addition, this moves the clusterctl config from the site
level to become its own function, which can be further refined
(e.g. for public cloud providers) via inheriting functions, composites,
types, etc.
Change-Id: Ic2b02e256419ee8536f5237327cce2754fd0abff
Closes: https://github.com/airshipit/airshipctl/issues/316
* fix the order of set context/set manifest commands
to configure ~/airship/.config
* fix broken tables in the markdown
* add section to tear down the cluster
Change-Id: I24828160bb0da9ec385d3b9493699eda165f8e3a
* add documentation for docker provider (capd)
* add manifests for docker provider (capd)
* add cluster templates for control plane and workers
* add site definition to use docker provider (capd) with
control plane and workers
Change-Id: I36a643774ce2e468b70ab29568bface3da537d41
