Alex Negulescu alecs

之前在这里研究过的用iptables配置跨网段的端口转发

Assume we have the following network environments:

Device:
- eth0 (192.168.6.59): for external access
- enx000ec6a490c5 (192.168.1.2): for ip camera
IP Camera：192.168.1.10
PC：192.168.6.2

On-Prem RKE2 api-server HA with Kube-VIP

               ,        ,  _______________________________
   ,-----------|'------'|  |                             |
  /.           '-'    |-'  |_____________________________|
 |/|             |    |    
   |   .________.'----'    _______________________________
   |  ||        |  ||      |                             |
   \__|'        \__|'      |_____________________________|

The following is taken from a brilliant answer on unix.se. Posting it here for personal reference. The question was:

What kind of patterns can I use in zsh parameter expansion?

${var//pattern/replacement} is using zsh wildcard patterns for pattern, the same ones as used for filename generation aka globbing which are a superset of the sh wildcard patterns. The syntax is also affected by the kshglob and extendedglob options. The ${var//pattern/replacement} comes from the Korn shell initially.

I'd recommend enabling extendedglob (set -o extendedglob in your ~/.zshrc) which gives you the most features (more so than standard EREs) at the expense of some backward incompatibility in some corner cases.

You'll find it documented at info zsh 'filename generation'.

On the host

Ensure these modules are loaded

cat /proc/sys/net/bridge/bridge-nf-call-iptables

Disable swap

sysctl vm.swappiness=0
swapoff -a

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

	'''
	Script to archive Slack messages from a channel list.
	You have to create a Slack Bot and invite him to private channels.
	View https://github.com/docmarionum1/slack-archive-bot for how to configure your account.
	Then provide the bot token to this script with the list of channels.
	'''

	TOKEN='xoxb-xxxxx-xxxxxx-xxxxxxxxxxx'

	channels = {

	rbac:
	create: true

	podSecurityPolicy:
	enabled: false

	imagePullSecrets:
	# - name: "image-pull-secret"

	## Define serviceAccount names for components. Defaults to component's fully qualified name.

	# disable sleep
	sudo pmset -b sleep 0; sudo pmset -b disablesleep 1

	# re-enable sleep
	sudo pmset -b sleep 5; sudo pmset -b disablesleep 0

	CC = gcc
	RM = rm -f

	INSTRUMENT_FOR_PROMETHEUS := false

	ifeq ($(INSTRUMENT_FOR_PROMETHEUS),true)
	CFLAGS = -Wall -DINSTRUMENT_FOR_PROMETHEUS
	LIBS = -lbcm2835 -lprom -lpromhttp -lmicrohttpd
	else
	CFLAGS = -Wall

	#!/bin/bash

	set -e

	CH=latest

	echo Installing Server 1
	k3sup install --user pi --ip 192.168.2.147 \
	--k3s-channel $CH \
	--cluster \