f5cf2d379a
The commit adds applier object from cli-utils which would allow us to wait for kubernetes objects to reach required states and support pruning. Integration is very similar to the one with kubectl, because backend mechanism for reading manifests is the same. We need to write them to temporary directory in $HOME/.airship directory, and point cli-utils to it. It will then take care of storing what was applied to k8s cluster for prunning and also will be capable of waiting for core resources to reach required state by constantly polling them. To integrate we need to create a namespace in which we will store configmap that keeps track of what objects were applied before and enable prunning Relates-To: #238 Change-Id: I4c0123cc57b78bd13dbe320e0ab9f28bbed2301d
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.