Stanislav Egorov 88d676a567 Proxy config for workers/workload
New replacements provide ability to use proxy configuration for worker nodes
and workload deployment.

To use proxy the following env vars should be exported for the session when
running phases: HTTP_PROXY, HTTPS_PROXY and NO_PROXY

Make sure to define all of them, especially NO_PROXY. For example, without
adding cluster IP addresses the deployment will fail.

Change-Id: Id08126f77e0a9da31318f1a239c51a6c78a7c88e
2020-10-26 16:54:30 +00:00
2020-05-19 13:45:09 +00:00
2020-05-20 16:07:49 -05:00
2019-06-25 08:11:57 -05:00
2020-08-05 13:22:59 +00:00
2020-10-21 18:15:03 +00:00
2020-10-21 18:15:03 +00:00
2019-10-19 14:16:05 -05:00
2020-08-25 17:37:19 -05:00

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.

Description
A CLI for managing declarative infrastructure.
Readme 380 MiB
Languages
Go 85.7%
Shell 9.6%
Dockerfile 1.4%
Jinja 1.3%
Makefile 1.2%
Other 0.8%