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.
 
 
 
 
 
 
Go to file
Matt McEuen 70ec47096c
Add catalogue-driven CAPI container versions
2 years ago
.github Update Airship vulnerability link 3 years ago
certs Adding the ability to inject certificate authorities into docker image 3 years ago
cmd Remove pkg/environment module 2 years ago
docs Fix docker provider (capd) documentation 2 years ago
manifests Add catalogue-driven CAPI container versions 2 years ago
pkg Implement phase and phase.Client interface 2 years ago
playbooks Enhance log collection zuul jobs 2 years ago
roles Worker node deployment 2 years ago
testdata/k8s Switch to Ubuntu focal (20.04) based image 3 years ago
tests/ansible Reusing apache-server instead of httpd 3 years ago
testutil Move bootstrapInfo config section to manifests 2 years ago
tools Merge "Add node availability check for deploy initinfra script" 2 years ago
zuul.d Enhance log collection zuul jobs 2 years ago
.gitignore Fix typo in .gitignore 3 years ago
.gitreview Gerrit: Add .gitreview file 4 years ago
.golangci.yaml Replace Non-ASCII symbols 3 years ago
CONTRIBUTING.md Guideline against very large Gerrit Changes 3 years ago
Dockerfile Adding the ability to inject certificate authorities into docker image 3 years ago
LICENSE Add LICENSE 3 years ago
Makefile Merge "improve logging" 2 years ago
README.rst Update stale README and reformat docs 3 years ago
Vagrantfile [#32]: scripts for local run playbooks 3 years ago
go.mod Merge "Add poller" 2 years ago
go.sum Merge "Add poller" 2 years ago
main.go Refactor airshipctl root command 2 years ago
tox.ini Replace venv with tox for documentation builds 3 years 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.