A CLI for managing declarative infrastructure.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Zuul 41d353444f Merge "Image override for CAPO components" 11 hours ago
.github Github action to create release notes 2 months ago
certs Adding the ability to inject certificate authorities into docker image 9 months ago
cmd Remove unnecessary constants 5 days ago
docs Add phase tree command in cmd module 1 week ago
krm-functions Update Go base images 2 months ago
manifests Image override for CAPO components 1 day ago
pkg Merge "Fix pulling docs from remote branch" 4 days ago
playbooks Add encryption to gates 1 day ago
roles change libvirt-bin package 6 days ago
testdata/k8s Revert "Encrypt and decrypt using sops" 2 months ago
tests/ansible Reusing apache-server instead of httpd 8 months ago
testutil Move MockDocument implementation to testutils 1 month ago
tools Merge "Fix golint check" 1 day ago
zuul.d Removing the non-voting jobs from dependency 1 day ago
.gitignore Fix typo in .gitignore 8 months ago
.gitreview Gerrit: Add .gitreview file 1 year ago
.golangci.yaml Replace Non-ASCII symbols 5 months ago
.grenrc.js Github action to create release notes 2 months ago
CONTRIBUTING.md Guideline against very large Gerrit Changes 6 months ago
Dockerfile Add commit and other labels to the airshipctl container image 1 week ago
LICENSE Add LICENSE 1 year ago
Makefile Add commit and other labels to the airshipctl container image 1 week ago
README.rst Update stale README and reformat docs 8 months ago
Vagrantfile [#32]: scripts for local run playbooks 10 months ago
go.mod Fix golint check 5 days ago
go.sum Fix golint check 5 days ago
main.go Refactor airshipctl root command 4 months ago
tox.ini Replace venv with tox for documentation builds 8 months ago

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.