0ef0f559f4
The controlplane phase renders node02, which for demo purposes uses an "example" hardwareProfile. However, it doesn't kustomize in the hardwareprofile-example, resulting in a null "firmware" attribute in the BMH. This change includes the hardwareprofile-example, and executes its replacement configuration to add itself into the hostgenerator. Change-Id: I4f7b8398384dff52011e8a034ccd798e5afaca1d
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.