v1k0d3n

bj916b at ATTOSXLT01-BJ916B in ~/working/working/charts/stable (master●●)
$ kubectl get pods -o wide --all-namespaces -w
NAMESPACE     NAME                                        READY     STATUS    RESTARTS   AGE       IP             NODE
default       hasty-grasshopper-jenkin-4005416353-99j15   0/1       Pending   0          9s        <none>
default       weave-scope-agent-79kdr                     1/1       Running   0          1d        192.168.3.22   kubenode02
default       weave-scope-agent-9b6ng                     1/1       Running   0          1d        192.168.3.24   kubenode04
default       weave-scope-agent-9cc2p                     1/1       Running   0          1d        192.168.3.23   kubenode03
default       weave-scope-agent-mjg20                     1/1       Running   1          1d        192.168.3.21   kubenode01
default       weave-scope-agent-p5z39                     1/1       Running   0          1d        192.168.3.25   kubenode05
default       weave-scope-app-1305666142-mnqw5       

v1k0d3n

# This ConfigMap is used to configure a self-hosted Calico installation.
kind: ConfigMap
apiVersion: v1
metadata:
  name: calico-config
  namespace: kube-system
data:
  # The location of your etcd cluster.  This uses the Service clusterIP
  # defined below.
  etcd_endpoints: "http://10.96.232.136:6666"

v1k0d3n

# You'll most likely need to adjust this for your env
minikube start \
      --network-plugin=cni \
      --kubernetes-version v1.5.1 \
      --disk-size 40g \
      --memory 16384 \
      --cpus 4 \
      --vm-driver kvm \
      --iso-url=https://storage.googleapis.com/minikube/iso/minikube-v1.0.4.iso
kubectl create -f http://docs.projectcalico.org/v2.0/getting-started/kubernetes/installation/hosted/calico.yaml

v1k0d3n

WARNING: WIP - Because I, like everyone else these days, have about 26 minutes before ADD takes over.

## DEPLOYING CLUSTER:
# Modify the version of Kubernetes for your deployment (at the time of writing, v1.5.3):
vi /home/bjozsa/kubelab/kubebuild/group_vars/all.yml

# Deploy Kubernetes Cluster (Ansible + Kubeadm):
ansible-playbook -i /home/bjozsa/kubelab/kubebuild/inventory.yml /home/bjozsa/kubelab/kubebuild/kube-deploy.yml

# Download the latest `kubectl` binary:

v1k0d3n

wget https://gist.githubusercontent.com/v1k0d3n/a38cc3febb53819e074dc322b9473f2f/raw/7234224ba34fd2891a29cbe544637d23f931db89/bootkube-clean.sh
wget https://gist.githubusercontent.com/v1k0d3n/a38cc3febb53819e074dc322b9473f2f/raw/057243cf033f44ce4b4a053d341c5b1723eabcab/bootkube-up.sh
chmod +x bootkube-*
./bootkube-up.sh

v1k0d3n

# Calico Version v2.6.1
# https://docs.projectcalico.org/v2.6/releases#v2.6.1
# This manifest includes the following component versions:
#   calico/node:v2.6.1
#   calico/cni:v1.11.0
#   calico/kube-controllers:v1.0.0

# This ConfigMap is used to configure a self-hosted Calico installation.
kind: ConfigMap
apiVersion: v1

v1k0d3n

Keybase proof

I hereby claim:

• I am v1k0d3n on github.
• I am v1k0d3n (https://keybase.io/v1k0d3n) on keybase.
• I have a public key ASBYzkbUstXG0bQCGbDF2CduJpn_Y3vLXGNtg41o7m7VzQo

To claim this, I am signing this object:

v1k0d3n

Introduction

Setting up an OS to work with xhyve can be a bit tricky, but it's not impossible. These intructions should be generally applicable to most versions of Linux.

Create a disk image file

Xhyve will use a file as a logical disk. Be sure you have the filesize you need, because growing the file later is tricky to impossible (you could try to use qcow or similar to get around this, but qcow volumes can be tricky to mount).

dd if=/dev/zero of=hdd.img bs=1g count=32 # Create a 32 gig disk. Raise 'count' as desired

v1k0d3n

kubernetes all in one

grab an atomic host

$ vagrant init fedora/25-atomic-host
$ vagrant up
$ vagrant ssh

v1k0d3n

# System preparation
## Update system:
sudo apt-get update && sudo apt-get dist-upgrade -y

## Prepare for Docker-CE install:
sudo apt-get install -y \
  apt-transport-https \
  ca-certificates \
  curl \
  gnupg-agent \