Currently, OpenStack-Helm-Infra uses version 2.11.0 of Kubernetes.
Because Airskiff uses OpenStack-Helm-Infra for deployment of K8s, newer
versions of Armada cause the Airskiff gate to fail, as Armada now uses
Tiller v2.12.1. This commit pins Armada to the latest version that
utilized Tiller v2.11.0. This pin should be removed as soon as
OpenStack-Helm-Infra moves to v2.12.1.
Currently, the latest version of OpenStack-Helm-Infra is used to
bootstrap a Kubernetes cluster and all required charts for the Armada
bootstrap process. Any breaking change in OSH-Infra can cause
inadvertent gate failures in the Airskiff gate even if the integration
itself is not broken. This commit pins all references during the
Airskiff setup process to known commit
f915a85f2ba8ad2f59044c5b8ad733d013a12e25 to prevent inadvertent gate
failures. The latest integration of OSH-infra and Airship remains tested
through regular uplift patches submitted by "Jenkins Uplifter
This change introduces Airskiff (see ), a development/learning environment
for the software delivery components of Airship, to the Airship-Treasuremap
repository. This change also adds a set of scripts accompanied by documentation
for easy deployment. During deployment, Armada, Deckhand, Pegleg, and Shipyard
are downloaded and built from source. Gate scripts from the OpenStack-Helm
project deploy a KubeADM-adminstered cluster. Armada deploys Armada, Deckhand,
and Shipyard into the cluster. The Airship components deploy OpenStack using
the documents provided by the Airskiff site. Airskiff is not safe for
production and should not be duplicated for production usage.