Skip to content

Instantly share code, notes, and snippets.

@danehans

danehans/Steps

Last active December 16, 2016 13:11
Show Gist options
  • Save danehans/ef71714b9ce44b14961ec32a26b4c7c4 to your computer and use it in GitHub Desktop.
Save danehans/ef71714b9ce44b14961ec32a26b4c7c4 to your computer and use it in GitHub Desktop.
Download ZIP
vagrant_vbox_kubeadm
Raw
provision.sh
#!/usr/bin/env bash
sudo su
yum update -y
cat <<EOF > /etc/yum.repos.d/kubernetes.repo
[kubernetes]
name=Kubernetes
baseurl=http://yum.kubernetes.io/repos/kubernetes-el7-x86_64
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://packages.cloud.google.com/yum/doc/yum-key.gpg
https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg
EOF
setenforce 0
yum install -y docker kubelet kubeadm kubectl kubernetes-cni
systemctl enable docker && systemctl start docker
systemctl enable kubelet && systemctl start kubelet
Raw
Steps
# Install Vagrant on your Mac: https://www.vagrantup.com/
# Here is the version I use
$ vagrant --version
Vagrant 1.8.1
# Virtualbox (vbox) is the default Vagrant provider, so it should be installed with Vagrant.
# I use vbox v5.0.16. If you need to install vbox, follow these directions: https://www.virtualbox.org/
# Copy the Vagrant file in this gist to your laptop.
# From the directory containing the Vagrant file, run:
$ vagrant up
# Note: You may be prompted to update your box. If so, do:
$ vagrant box update
# After your vagrant box completes the build is ready, ssh to it:
$ vagrant ssh
# Now you are ready to use kubeadm to configure the server.
# Perform these steps:
sudo su
kubeadm init
kubectl taint nodes --all dedicated-
kubectl apply -f https://git.io/weave-kube
# Ref: kubeadm guide: http://kubernetes.io/docs/getting-started-guides/kubeadm/
#
# Notes:
# 1. You only need 1 vbox server for development purposes.
# 2. Taint command is used, since there is only one node
# 3. Make note of the kubeadm join command at the end of kubeadm init, in case you want to add nodes in future.
#
# Ensure everything comes up
kubectl get pods --all-namespaces
Raw
tests
# I followed the e2e doc for testing k8s. My usecase was e2e performance tests.
# e2e test doc: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/e2e-tests.md
# Please spend time reviewing the details of the e2e test doc.
# Fork the k8s project.
# Vagrant ssh to your k8s server, clone your k8s fork and change to the k8s project directory.
# Run the e2e tests.
# Since we have a local k8s cluster running (mac/vagrant/vbox/kubeadm), we need to use KUBERNETES_PROVIDER=skeleton.
# If your k8s client/api versions do not match, set --check_version_skew=false
# Provide the location of your kubeconfig file: --kubeconfig="/etc/kubernetes/admin.conf"
# Provide the ip/port of your k8s api server: --host="https://10.0.2.15:443"
# Provide the path to your local k8s project repo: --repo-root="/root/code/go/src/github.com/kubernetes/kubernetes"
# Review the above guide for more details. The following is a working example:
$ KUBERNETES_PROVIDER=skeleton go run hack/e2e.go -v --test --check_version_skew=false --test_args="--ginkgo.focus=resource\susage\stracking --host="https://10.0.2.15:443" --kubeconfig="/etc/kubernetes/admin.conf" --repo-root="/root/code/go/src/github.com/kubernetes/kubernetes""
Raw
Vagrantfile
# -*- mode: ruby -*-
# vi: set ft=ruby :
# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure(2) do |config|
# The most common configuration options are documented and commented below.
# For a complete reference, please see the online documentation at
# https://docs.vagrantup.com.
# Every Vagrant development environment requires a box. You can search for
# boxes at https://atlas.hashicorp.com/search.
config.vm.box = "centos/7"
# Disable automatic box update checking. If you disable this, then
# boxes will only be checked for updates when the user runs
# `vagrant box outdated`. This is not recommended.
# config.vm.box_check_update = false
# Create a forwarded port mapping which allows access to a specific port
# within the machine from a port on the host machine. In the example below,
# accessing "localhost:8080" will access port 80 on the guest machine.
# config.vm.network "forwarded_port", guest: 80, host: 8080
# Create a private network, which allows host-only access to the machine
# using a specific IP.
# config.vm.network "private_network", ip: "192.168.33.10"
# Create a public network, which generally matched to bridged network.
# Bridged networks make the machine appear as another physical device on
# your network.
# config.vm.network "public_network"
# Share an additional folder to the guest VM. The first argument is
# the path on the host to the actual folder. The second argument is
# the path on the guest to mount the folder. And the optional third
# argument is a set of non-required options.
# config.vm.synced_folder "../data", "/vagrant_data"
# Provider-specific configuration so you can fine-tune various
# backing providers for Vagrant. These expose provider-specific options.
# Example for VirtualBox:
#
config.vm.provider "virtualbox" do |vb|
# # Display the VirtualBox GUI when booting the machine
# vb.gui = true
#
# Customize the amount of memory on the VM:
vb.memory = "6144"
end
#
# View the documentation for the provider you are using for more
# information on available options.
# Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
# such as FTP and Heroku are also available. See the documentation at
# https://docs.vagrantup.com/v2/push/atlas.html for more information.
# config.push.define "atlas" do |push|
# push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
# end
# Enable provisioning with a shell script. Additional provisioners such as
# Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
# documentation for more information about their specific syntax and use.
# config.vm.provision "shell", inline: <<-SHELL
# sudo apt-get update
# sudo apt-get install -y apache2
# SHELL
# Perform prerequisite steps for kubeadm
config.vm.provision "shell", path: "./provision.sh", privileged: true
end
@pmichali
Copy link

pmichali commented Dec 2, 2016

Check out my fork and see if you want to pull in the changes. I increased the VM memory from the default of 512MB to 6GB and added a script to do some of the preliminary provisioning work.

@danehans
Copy link
Author

@shmcfarl added the following for IPv6:

   config.vm.provider "virtualbox" do |vb|
     vb.name = "k8s-aio"
   config.vm.hostname = "k8s-aio"
   end
   config.vm.network "private_network", ip: "192.168.20.10"
   config.vm.network "private_network", ip: "2001:db8:cafe:14::a"
 end

@pmichali
Copy link

pmichali commented Dec 16, 2016 •
edited
Loading

Please see https://cisco.jiveon.com/people/pcm/blog/2016/12/05/kubernetes-development-environments-that-work, where I could I had to bump the # of CPUs for the cluster to come up properly (on my MacBook).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment