Thiago Navarro navarrothiago

Set up microk8s with Cilium for development

Microk8s is a Canonical project to provide a kubernetes environment for local development, similar to minikube but without requiring a separate VM to manage. These instructions describe setting it up for common development use cases with Cilium and may be helpful in particular for testing BPF kernel extensions with Cilium.

Microk8s will run its own containerd runtime, which may be initially confusing when building containers locally with docker. This guide assumes that you will use docker locally for building containers, and push these into a microk8s registry for use by containerd in the microk8s environment.

This guide works with MicroK8s 1.14 or above, with containerd. If you are running an earlier version, see the previous instructions.

Requirements

Ramp up your Kubernetes development, CI-tooling or testing workflow by running multiple Kubernetes clusters on Ubuntu Linux with KVM and minikube.

In this tutorial we will combine the popular minikube tool with Linux's Kernel-based Virtual Machine (KVM) support. It is a great way to re-purpose an old machine that you found on eBay or have gathering gust under your desk. An Intel NUC would also make a great host for this tutorial if you want to buy some new hardware. Another popular angle is to use a bare metal host in the cloud and I've provided some details on that below.

We'll set up all the tooling so that you can build one or many single-node Kubernetes clusters and then deploy applications to them such as OpenFaaS using familiar tooling like helm. I'll then show you how to access the Kubernetes clusters from a remote machine such as your laptop.

Pre-reqs

This tutorial uses Ubuntu 16.04 as a base installation, but other distributions are supported by KVM. You'll need to find out how to install

Package Management in C++ with Conan for Beginners

C++ package management can be complicated.

Below are some key tools involved:

Make

Make runs commands defined in a Makefile, for example, to build and install programs with the compiler and linker. For our purposes, we won't worry about what this looks like; you only need to understand its purpose in relation to CMake.

Effective Modern CMake

Getting Started

For a brief user-level introduction to CMake, watch C++ Weekly, Episode 78, Intro to CMake by Jason Turner. LLVM’s CMake Primer provides a good high-level introduction to the CMake syntax. Go read it now.

After that, watch Mathieu Ropert’s CppCon 2017 talk Using Modern CMake Patterns to Enforce a Good Modular Design (slides). It provides a thorough explanation of what modern CMake is and why it is so much better than “old school” CMake. The modular design ideas in this talk are based on the book [Large-Scale C++ Software Design](https://www.amazon.de/Large-Scale-Soft

Switching between AHCI and RAID on the Dell XPS 15 (9560)

This guide likely applies to other models and, potentially, even laptops from other OEMs that have NVME drives. However, I've only tested this on my Dell XPS 15 (9560) with the OEM Windows installation from the Signature Edition model.

Switching from RAID to AHCI

Switching from RAID to AHCI is significantly simpler than switching from AHCI to RAID. All that's needed is a successful boot to Safe Mode.

To set the default boot mode to Safe Mode, use msconfig.exe or open an admin cmd/PowerShell window and run:

Redhawk on Raspberry Pi

One option for compiling Redhawk for the Raspberry Pi is using QEMU on a host to compile it into the image before loading on the rpi hardware - this takes advantage of the superior hardware on your host to decrease compile time. These instructions verified for host system Ubuntu 16.04, Raspberry Pi image Raspbian Stretch 2017-09-07, and Redhawk 2.0.7.

It is important to note that Redhawk is only officially supported on CentOS 6 and 7 and therefore any time you try to compile it for other OS's it's possible (likely on systems like Ubuntu/Debian) that you'll have issues with newer versions of dependencies, the most likely offenders in the past have been:

Library	CentOS 6.9	CentOS 7.4	Ubuntu 16.04	Debian 9.2	Raspbian Stretch	Fedora 28
gcc	4.4.7	4.8.5	5.4.0	6.3.0	6.3.0	8.1.1
libstdc++	4.4.7	4.8.5	5.4.0	6.3.0	6.3.0	8.1.1

Vim cheat sheet

Starting Vim

vim [file1] [file2] ...

	{
	"workbench.startupEditor": "newUntitledFile",
	"editor.fontSize": 16,
	"editor.lineHeight": 1.8,
	"javascript.suggest.autoImports": true,
	"javascript.updateImportsOnFileMove.enabled": "always",
	"editor.rulers": [
	80,
	120
	],

	#!/bin/bash -xeu

	# let host and guests talk to each other over macvlan
	# configures a macvlan interface on the hypervisor
	# run this on the hypervisor (e.g. in /etc/rc.local)
	# made for IPv4; need modification for IPv6
	# meant for a simple network setup with only eth0,
	# and a static (manual) ip config
	# Evert Mouw, 2013

	set(LIBFOO_TAR_HEADERS
	"${CMAKE_CURRENT_BINARY_DIR}/include/foo/foo.h"
	"${CMAKE_CURRENT_BINARY_DIR}/include/foo/foo_utils.h"
	)

	add_custom_command(OUTPUT ${LIBFOO_TAR_HEADERS}
	COMMAND ${CMAKE_COMMAND} -E tar xzf "${CMAKE_CURRENT_SOURCE_DIR}/libfoo/foo.tar"
	COMMAND ${CMAKE_COMMAND} -E touch ${LIBFOO_TAR_HEADERS}
	WORKING_DIRECTORY "${CMAKE_CURRENT_BINARY_DIR}/include/foo"
	DEPENDS "${CMAKE_CURRENT_SOURCE_DIR}/libfoo/foo.tar"