43d4ebe164
This change adds an environment variable override to change the metadata path in the Airship config file when using the CI-driven deployment scripts. This will enable the Treasuremap repository to store metadata.yaml at the site level while using the same deployment scripts from airshipctl. Change-Id: I0862a87417ad7a4d8666df7b34e25327bb40e251 Signed-off-by: Drew Walters <andrew.walters@att.com> |
||
---|---|---|
.github | ||
certs | ||
cmd | ||
docs | ||
manifests | ||
pkg | ||
playbooks | ||
roles | ||
testdata/k8s | ||
tests/ansible | ||
testutil | ||
tools | ||
zuul.d | ||
.gitignore | ||
.gitreview | ||
.golangci.yaml | ||
CONTRIBUTING.md | ||
Dockerfile | ||
LICENSE | ||
Makefile | ||
README.rst | ||
Vagrantfile | ||
go.mod | ||
go.sum | ||
main.go | ||
tox.ini |
README.rst
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.