4810509fa3
A previous patchset was intended to accomplish a two-part substitution of container versions into CAPI components, to work around assumptions held by clusterctl: (versions catalogue) --[ReplacementTransformer]--> (Clusterctl YAML) ... then (Clusterctl YAML) --[clusterctl library]--> (CAPI manifests) However, only the second leg (the hard part) worked right; the first part had gaps which are fixed by this change. This also adds the CAPD container definitions to the Clusterctl variables. Change-Id: Ifaca46f6dd3b87c28753cd49b52e62556ead52bd Closes: https://github.com/airshipit/airshipctl/issues/389
Airshipctl
Airshipctl is a command-line interface that enables users to manage declarative infrastructure and software.
Airshipctl aims to provide a seamless experience for operators wishing to leverage the best open source options such as the Cluster API, Metal Kubed, Kustomize, and kubeadm by providing a straight forward and easily approachable interface.
This project is the heart of our effort to produce Airship 2.0, which has three main evolutions from Airship 1.0:
- Expand our use of entrenched upstream projects.
- Embrace Kubernetes Custom Resource Definitions (CRD) – everything becomes an object in Kubernetes.
- Make the Airship control plane ephemeral.
To learn more about the Airship 2.0 evolution, reference the Airship blog series.
Contributing
Airshipctl is under active development and welcomes new developers! Please read our developer guide to begin contributing.
We also encourage new contributors and operators alike to join us in our Slack workspace and subscribe to our mailing lists.
You can learn more about Airship on the Airship wiki.