mak3r

# encoding: utf-8
# -*- mode: ruby -*-
# vi: set ft=ruby :

#put <<FYI
# create a virtualbox vm with the latest version of kubectl
# vagrant up 
# create a virtualbox vm with a specific version of kubectl
# KUBECTL_VER=v1.9.7 vagrant up 
#FYI

mak3r

FROM ubuntu:18.04

# default kubectl version is current stable
# override this when building the container to use a different version
ARG KUBECTL_VER='$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)'

WORKDIR /app

# include my kubeconfig in the container
COPY kubeconfig /app/kubeconfig

mak3r

#!/bin/bash

# based on 
# https://rancher.com/docs/rancher/v2.x/en/upgrades/upgrades/single-node-upgrade/

RANCHER_CONTAINER_NAME=$1
RANCHER_CONTAINER_TAG=$2
RANCHER_VERSION=$3
RANCHER_UPGRADE_VERSION=$4

mak3r

air-gap Rancher install

This is an unofficial documentation of what I did to setup the Rancher v2 air-gap HA install

Official docs are here https://rancher.com/docs/rancher/v2.x/en/installation/air-gap-high-availability/

mak3r

Prep

1. Generate a list of instances

• sbin/generate-instance-list.sh -n mak3r-rancher-training-k3s > instance-ids.json
• use a script to connect to those instances by list id
  • sbin/ssh-connect.sh -i 0 -k ~/.ssh/mak3r-private.pem -s

2. Get the cloud server public IP address and replace throughout the script
3. Prepare a local RPi server

---

mak3r

Prep

1. Generate a list of instances

• sbin/generate-instance-list.sh -n mak3r-rancher-training-k3s > instance-ids.json
• use a script to connect to those instances by list id
  • sbin/ssh-connect.sh -i 0 -k ~/.ssh/mak3r-private.pem -s

2. Get the cloud server public IP address and replace throughout the script
3. Prepare a local RPi server

---

mak3r

Access aws instances easily even after dns name changes

Restarts of aws ec2 instances can cause ips and dns names to change if you don't pay for static IPs

This set of scripts enables quick ssh access to a group of similarly named machines

1. run generate-instance-list.sh to get a list of aws instance ids
2. run ssh-connect.sh against the generated list to access any of the instances

TODO

Currently it is not possible to differentiate the machines easily - enable access by more human readable names in the generated instance list.

mak3r

Packer and Vagrant resources to build k3os in VirtualBox

Requirements

• packer
• vagrant
• virtualbox

Build and Run

1. packer build k3os.json
2. vagrant up

mak3r

Demo at Arm TechCon 2019

Executive Materials

Summary https://rancher.com/blog/2019/rancher-and-arm-partner-to-accelerate-edge-computing

White paper https://info.rancher.com/accelerating-edge-computing-with-arm-and-k3s-lightweight-kubernetes

Technical Materials

mak3r

for i in $(docker ps | cut -f 1 -d " " | grep -v CONTAINER); do docker stop $i; docker rm $i; done