114ee09301
All KubeadmControlPlane, Metal3Cluster, and Metal3MachineTemplates must reside in the same namespace to which ViNO applies BMH objects. This change updates the LMA sub-cluster CAPI namespace reference within the airhsipctl cluster map to vino-system, where all of those objects reside. This change also modifies the Kustomiza entrypoints that deploy CAPI objects to deploy them into the same namesapce. Signed-off-by: Drew Walters <andrew.walters@att.com> Change-Id: Ie8f8516326d505c290d6d4ac04ef50fa900e62da |
||
|---|---|---|
| .. | ||
| README.md | ||
| cluster_map_patch.yaml | ||
| executors.yaml | ||
| kustomization.yaml | ||
| phases.yaml | ||
| validation-config.yaml | ||
| workload-config.yaml | ||
README.md
Phases for multi-tenant type
Phases defined in multi-tenant are available for use by sites that inherit type mulit-tenant.
Airshipctl phase command
For deploying calico network v3 policies, a phase named
deliver-network-policy is defined with its executor and configMap settings.
To deploy network policy using airshipctl, do
airshipctl phase run deliver-network-policy where deliver-network-policy is the phase name.
For deleting network policy, a phase named delete-network-policy is defined with its executor and configMap settings.
To delete network policy using airshipctl, do
airshipctl phase run delete-network-policy where delete-network-policy is the phase name.