
When reconciling clusters, airshipctl points the bootstrapInfo and managementConfiguration to an entry named default, and the user is unaware of this change. The result is that user settings are ignored unless the user defines settings under entries named "default". This change updates the cluster reconciliation logic to do this only when a cluster is added to the airshipconfig by airshipctl. Fixes #244 Change-Id: I2cefbf83a74d9cd566015509a4f768698d274746 Signed-off-by: Drew Walters <andrew.walters@att.com>
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.