6dc39f0735
The proposed workflow is more generalized and conforms with other k8s tools like kubectl in the way of using kubeconfig. airshipctl will use single kubeconfig file (by default located at ~/.kube/config), and this file will be managed (adding/removing contexts) via KRM function named kubeconfig-manager. Change-Id: I9764eaf9665eaac5543b91c6c876094dfe23a86f Signed-off-by: Ruslan Aliev <raliev@mirantis.com> Closes: #666 |
||
---|---|---|
.github | ||
certs | ||
cmd | ||
docs | ||
krm-functions | ||
manifests | ||
pkg | ||
playbooks | ||
roles | ||
testdata/k8s | ||
tests/ansible | ||
testutil | ||
tools | ||
zuul.d | ||
.deadlink | ||
.gitignore | ||
.gitreview | ||
.golangci.yaml | ||
.goreleaser.yaml | ||
.grenrc.js | ||
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.