| #!/bin/bash | |
| # ofed-ubuntu.sh | |
| # Install Mellanox Ofed on Ubuntu Machines | |
| # | |
| # Author: Nilson Lopes (06/17/2021) | |
| ubuntu_release=$(awk -F '"' '/VERSION_ID/ {print $2}' /etc/os-release) | |
| mofed_package_version='24.10-2.1.8.0' | |
| mofed_repo_base_url="https://linux.mellanox.com/public/repo/mlnx_ofed" |
| #!/bin/bash | |
| # | |
| BACKUPDEST="$1" | |
| DOMAIN="$2" | |
| MAXBACKUPS="$3" | |
| if [ -z "$BACKUPDEST" -o -z "$DOMAIN" ]; then | |
| echo "Usage: ./vm-backup <backup-folder> <domain> [max-backups]" | |
| exit 1 |
DB
ovs-vsctl list open_vswitch
ovs-vsctl list interface
ovs-vsctl --columns=ofport,name list Interface
ovs-vsctl --columns=ofport,name --format=table list Interface
ovs-vsctl -f csv --no-heading --columns=_uuid list controller
ovs-vsctl --format=table --columns=name,mac_in_use find Interface name=br-dpdk1
ovs-vsctl get interface vhub656c3cb-23 name
The official guide for setting up Kubernetes using kubeadm works well for clusters of one architecture. But, the main problem that crops up is the kube-proxy image defaults to the architecture of the master node (where kubeadm was run in the first place).
This causes issues when arm nodes join the cluster, as they will try to execute the amd64 version of kube-proxy, and will fail.
It turns out that the pod running kube-proxy is configured using a DaemonSet. With a small edit to the configuration, it's possible to create multiple DaemonSets—one for each architecture.
Follow the instructions at https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/ for setting up the master node. I've been using Weave Net as the network plugin; it see