Community Contributions And Screencasts Getting Airship CNCF Certified: CNCF Conformance and CIS Benchmark Tests Using Sonobuoy https://hackmd.io/2euwW6srTVSV2C2mxVOS7g Testing Local K8s Cluster Development Workflows with Airship: Airshipctl and Cluster API Docker https://hackmd.io/yJDorM4gSwmyRuf7Kh7HZg Creating Production Grade K8s Cluster on GCP with Airship: Airshipctl and Cluster API GCP https://hackmd.io/hTy5BVlbSxmPHVi-u4HcKQ

This document provides instructions on using clusterctl to deploy a self-managed workload cluster on google cloud. The purpose of testing the gcp provider using clusterctl is to evaluate the current state of cluster api - gcp provider, and gauge the overall effort that will be required to implement airshipctl and cluster api gcp integration. Check Takeaways Also check Airshipctl and Cluster api gcp integration Workflow A kind cluster initialized with capi and capg provider components, on local vm was used to create a workload cluster on google cloud with 1 machine deployment and 1 control plane. The workload cluster was later initialized with provider components, making it a capi target management cluster. Then, all the CAPI CRDs were moved from the kind management cluster to the target management cluster on google cloud using clusterctl move, thus making the workload cluster on google cloud self managed. $ kubectl get machines --kubeconfig ~/projects/cluster-api/gtc.kubeconfig

source management cluster: ~/.airship/kubeconfig (default) target management cluster: ~/capi-quickstart.kubeconfig ❯ kubectl get pods -A NAMESPACE NAME READY STATUS RESTARTS AGE capd-system capd-controller-manager-9cb5d94cc-tbzbm 1/1 Running 0 23m capi-kubeadm-bootstrap-system capi-kubeadm-bootstrap-controller-manager-b76dfc9c8-d6tpp 1/1 Running 0 23m capi-kubeadm-control-plane-system capi-kubeadm-control-plane-controller-manager-58dfcb7574-gklcz 1/1 Running 0 23m capi-system capi-controller-manager-6c8b76f9f4-7stx9 1/1 Running 0 23m

Configure Clone airshipctl and treasuremap in the user's home directory, checkout v2.0 on both repos create config ~/airship-config create a helper script (./setup_tr.sh) in user's home dir execute sudo ./setup_tr.sh airship@d101:~$ echo $PWD /home/airship

Repository Clone git clone git@bitbucket.org:rk_jain/javascriptfundamentals.git Reference https://www.w3schools.com/js/ Installation, Windows 1. Install virtual box, extension pack 2. install latest ubuntu

This document shows usage of airshipctl and cluster api docker provider (capd) using kind, to create a cluster api management kubernetes cluster with 1 control plane and 3 worker nodes. Getting Started Build Airshipctl $ git clone https://review.opendev.org/airship/airshipctl $ cd airshipctl $ ./tools/deployment/21_systemwide_executable.sh Setup Airship Config $ cat ~/.airship/config

Hi Matt, You have a valid question. It is just that in the past, we were using the workflow defined here: Reference: https://cluster-api.sigs.k8s.io/clusterctl/commands/move.html#bootstrap--pivot Bootstrap & Pivot The pivot process can be bounded with the creation of a temporary bootstrap cluster used to provision a target Management cluster.

In this document we execute the following phases, using docker provider(capd) ❯ airshipctl phase plan GROUP PHASE group1 clusterctl-init-ephemeral controlplane-ephemeral clusterctl-init-target clusterctl-move workers-target

In the document, we demonstrate the usage of the following phases with docker rovider(capd): ❯ airshipctl phase plan GROUP PHASE group1 clusterctl-init-ephemeral controlplane-ephemeral workers-ephemeral clusterctl-init-target clusterctl-move

Sonobuoy(so·​no·​buoy | \ ˈsä-nə-ˌbȯi , -ˌbü-ē ) is a diagnostic tool that makes it easier to understand the state of a Kubernetes cluster by running a set of plugins (including Kubernetes conformance tests) in an accessible and non-destructive manner. It is a customizable, extendable, and cluster-agnostic way to generate clear, informative reports about your cluster. Its selective data dumps of Kubernetes resource objects and cluster nodes allow for the following use cases: Integrated end-to-end (e2e) conformance-testing Workload debugging Custom data collection via extensible plugins. To check confromance results on cluster created with airshipctl, go to section Results

Overview Zuul Scripts for testing airshipctl and cluster api docker integration is being handled by the job - airship-airshipctl-gate-script-runner-dockertest, included in the patchset https://review.opendev.org/#/c/738682/ This document contains information on usage of the scripts in patchset https://review.opendev.org/#/c/738682/ to test airshipctl and cluster api docker integration locally. Airshipctl and cluster api docker integration is available as a part of patchset - https://review.opendev.org/#/c/737871/ For more information on airshipctl and cluster api docker integration visit Airshipctl And Cluster API Docker Integration

Overview Airshipctl and cluster api gcp integration facilitates usage of airshipctl to create cluster api management and workload clusters using gcp as infrastructure provider. Airshipctl and cluster api gcp integration is available as a part of patchset - https://review.opendev.org/#/c/748063/. This document provides information on usage of the patchset. Zuul scripts to test the cluster api gcp integration is available in patchset - https://review.opendev.org/#/c/749165/ Workflow A simple workflow that can be tested using the patchset, involves the following operations: Initialize the management cluster with cluster api and gcp provider components

Table of Contents Overview Workflow Common Pre-requisites Getting Started Create airshipctl configuration files Use the latest patchset Initialize the management cluster Create your first workload cluster