e2c56108ee
1. Extending templater with kyaml functions and creating combined catalogue to be able to request/update the existing resources. This is based on 'everything is transformer' concept introduced in kustomize 4.x That includes gathering all secrets into 1 variable catalogue and special mechanism to regenerate/merge with manual secrets. 2. Implementing 'catalogue per cluster' approach for secrets. 3. Rearranging secrets so it's possible to use: pgp (each person may have his own key), age, Hachicorp Vault and etc and the list of people who can decrypt documents is set in a special file. Since in some cases there should be a separate list of people who can decrypt data - this list is set for each cluster (ephemeral and target) separatelly. Closes: #586 Change-Id: I038f84dd138d5ad4a35f4862c61ff2124c2fd530 |
||
|---|---|---|
| .. | ||
| 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.