13c4e82f7e
It deploys 3 controlplane and 2 worker nodes using AIAP gate. + kubectl --context target-cluster get node NAME STATUS ROLES AGE VERSION node01 Ready control-plane,master 48m v1.21.2 node03 Ready worker 43s v1.21.2 node04 Ready control-plane,master 16m v1.21.2 node05 Ready control-plane,master 26m v1.21.2 node06 Ready worker 54s v1.21.2 Tested with 32 GB node. https://zuul.opendev.org/t/openstack/build/da1c2c440d3d4026ab454de73ee518e2/logs Closes: #652 Closes: #228 Change-Id: Ie2267e15ed75b57e2e27f45b9be19ddcf7b0a0a8 |
||
|---|---|---|
| .. | ||
| replacements | ||
| cluster.yaml | ||
| controlplane.yaml | ||
| kustomization.yaml | ||
| namespace.yaml | ||
| README.md | ||
Function: k8scontrol
This function defines a KubeADM and Metal3 control plane, including Cluster, Metal3Cluster, KubeadmControlPlane, and Metal3MachineTemplate resources.
Optional: a versions-airshipctl VersionsCatalogue 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.