6059f429e2
Add phase execution engine scaffolding to documentation. Also add general architecture of phases, and brief description of what phases, executors and bundles are. Next commits will fill in the placeholders and topics in the documentation, such as metadata and phase plan. Relates-To: #360 Change-Id: Icac00b046cf50d18a71ca69ef9ecbb8be612f9ab |
||
---|---|---|
.github | ||
certs | ||
cmd | ||
docs | ||
manifests | ||
pkg | ||
playbooks | ||
roles | ||
testdata/k8s | ||
tests/ansible | ||
testutil | ||
tools | ||
zuul.d | ||
.gitignore | ||
.gitreview | ||
.golangci.yaml | ||
CONTRIBUTING.md | ||
Dockerfile | ||
go.mod | ||
go.sum | ||
LICENSE | ||
main.go | ||
Makefile | ||
README.rst | ||
tox.ini | ||
Vagrantfile |
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.