The figure below calls out
- The netfilter hooks
- The order of table traversal
The goal of this document to cover all aspects of Kubernetes management, including how resources are expressed, constrained and accounted for. This started a way to ensure that alternate container runtime implementation like Kata containers will behave from a resource accounting and consumption point of view in the same manner as runc
.
Location of the latest version of this document: https://gist.github.com/mcastelino/b8ce9a70b00ee56036dadd70ded53e9f
If you do not understand cgroups please refer to a quick primer at the bottom of this document. This will help you understand how the resource enforcement actually works.
Note: virtio-serial does cannot be connected to a pcie bus. It does work when connected directly to the host bridge as a transistional virtio device. | |
This needs to be investigated | |
``` | |
#!/bin/bash | |
# -*- mode: shell-script; indent-tabs-mode: nil; sh-basic-offset: 4; -*- | |
# ex: ts=8 sw=4 sts=4 et filetype=sh | |
VMN=${VMN:=1} |
QEMU supports migration of a virtual machine across machine over the network. It also has the capability to save the state of a virtual machine and resume from that state.
It is described in detail in https://www.linux-kvm.org/page/Migration
This capability can be leveraged to create an instant resume virtual machine image if the virtual machine is crafted with care.
The Prometheus operator offers a simple method to scrape metrics from any Pod. However in many cases the Pod itself is not what you are monitoring but the Pod is used to expose metrics that relate to the Node. In such cases what the user cares about is the Node on which the Pod runs and not the Pod itself.
By default when using PodMonitor
all the time series data will have the instance
set to the Pod's name. Also the Pod or the Daemon set that the Pod was part of may be deleted, redeployed multiple times over the lifetime of the node. This means that the user will need to perform the mapping between the Pod and the Node on which it run.
However Prometheus allows the instance name (among other labels) to be relabeled in a very simple manner as shown below.
apiVersion: monitoring.coreos.com/v1
There are two ways you can talk to the KUBE API.
Start a kube proxy server which will act as a reverse proxy for the client.
This sets up a host local bridge with a macvlan interface for VM to host communication. The macvtap is setup with vhost support.
The command line options to note are
-netdev tap,fd=3,id=hostnet0,vhost=on,vhostfd=4 3<>$"$tapdev" 4<>/dev/vhost-net -device virtio-net-pci,netdev=hostnet0,id=net0,mac=$(< /sys/class/net/testtap/address)
This sets up two different fd's. The first for macvtap and the second for vhost-net.
How to launch multiple QEMU based VM's that can communicate with the outside world and between each other other without any setup on the host.
This uses two features available in qemu
This allows us to have