George Kal geokal

Using Multus CNI in K3S

By default, K3S will run with flannel as the CNI and use custom directories to store CNI plugin binaries and config files(You can inspect the kubelet args K3S uses via journalctl -u k3s|grep cni-conf-dir). So you need to configure that properly When deploying Multus CNI.

For example given the official Multus manifests in https://github.com/intel/multus-cni/blob/36f2fd64e0965e639a0f1d17ab754f0130951aba/images/multus-daemonset.yml, the following changes are needed:

volumes:
 - name: cni

Requirements

Minikube requires that VT-x/AMD-v virtualization is enabled in BIOS. To check that this is enabled on OSX / macOS run:

sysctl -a | grep machdep.cpu.features | grep VMX

If there's output, you're good!

Prerequisites

Migration guide for Windows VMs from Hyper-V

First get the virtual disk (vhdx) from the Hyper-V platform.

Use a Linux machine with libvirt installed.

Do not forget to install the UEFI firmware:

sudo apt install ovmf

update OS
factory reset

Spotify
logi options
- set mouse buttons to mission control

Installing homebrew / Linuxbrew on Ubuntu-18.04 wsl for Windows 10

open wsl command line

type -

sh -c "$(curl -fsSL https://raw.githubusercontent.com/Linuxbrew/install/master/install.sh)"

`kubectl` commands and tips&tricks for CKA, CKAD and CKS exams

Quickly retrieve imperative commands to create k8s resources.

Command: k run -h | grep '# ' -A2

When is it useful: copy/paste command to notepad, edit values and execute to create desired resource

Result: list of different ways to create k8s resources imperatively using kubectl

	---
	apiVersion: apps/v1
	kind: Deployment
	metadata:
	name: hello-blue-whale
	spec:
	replicas: 3
	selector:
	matchLabels:
	app: hello-whale-app

	---
	apiVersion: apps/v1
	kind: Deployment
	metadata:
	name: hello-blue-whale
	spec:
	replicas: 3
	selector:
	matchLabels:
	app: hello-whale-app

	<#
	Create Unix VM's.

	PREREQUISITES:
	- A VM that has been installed with an OS that supports cloud-init
	- cloud-init is installed on the vm

	How it works:
	- Asks for a bunch of parameters
	- Creates a disk from parent vhdx for speed

	const path = require('path')
	const fs = require('fs')
	const execSync = require('child_process').execSync

	if (!process.argv[2] \|\| !process.argv[3]) {
	throw new Error('you did not pass the source and destination paths')
	}

	const searchPath = path.join(process.cwd(), process.argv[2])
	const destination = path.join(process.cwd(), process.argv[3])