
This patchset introduces new field to Phase.Config API object SiteWideKubeconfig - if set to true, the phase will have access to all kubeconfigs for each cluster defined in ClusterMap. By default only kubeconfig of the cluster specified in Phase.Metadata.ClusterName will be available to the phase executor. This approach will speed up the deployment process because arishipctl will not have to look for multiple kubeconfigs when running each phase Closes: #547 Change-Id: Ic92027ba88d3ce8cb769c254968530037540b8fd
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.