
This adds a phase to wait for the target cluster to become initialized, directed at the ephemeral management cluster. It re-uses the helper script already used by the `kubectl-wait-cluster-target` phase, adds parameterization so that it can watch for both controlPlaneInitialized and controlPlaneReady conditions, and adds the new phase to the phase plan. Lack of this waiting was causing errors in some environments. This also adds a kubectl-wait-node-target phase definition, in case we ever want to make use of it. Change-Id: Ic18742dd59a7901b0d985b8c11260bc1b3527a30
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.