curl -Lo /tmp/kind https://kind.sigs.k8s.io/dl/v0.13.0/kind-linux-amd64
sudo install -o root -g root -m 0755 /tmp/kind /usr/local/bin/kind
curl --output /tmp/virtctl -L https://github.com/kubevirt/kubevirt/releases/download/$(curl -s https://api.github.com/repos/kubevirt/kubevirt/releases/latest | awk -F '[",]' '/tag_name/{print $4}')/virtctl-$(curl -s https://api.github.com/repos/kubevirt/kubevirt/releases/latest | awk -F '[",]' '/tag_name/{print $4}')-linux-amd64
sudo install -o root -g root -m 0755 /tmp/virtctl /usr/local/bin/virtctl
cat <<EOF > /tmp/kind.yaml && kind create cluster --config /tmp/kind.yaml
kind: Cluster
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
This GitHub Gist details the manual configuration needed on a UniFi controller to enable IPv6 tunneling with Hurricane Electric's Tunnelbroker service.
This is what works for me personally. Stuff you'll need to do to adapt this to your ends:
- Replace "local-ip" with your USG's public IPv4 address.
- Replace "remote-ip" with the address of your Tunnelbroker tunnel server.
- Replace "address" with the IPv6 address that your are allocated.
# 2017-10-01T14:14:44+00:00 | |
108.175.32.0/20 | |
108.175.34.0/24 | |
108.175.35.0/24 | |
192.173.64.0/18 | |
198.38.100.0/24 | |
198.38.101.0/24 | |
198.38.108.0/24 | |
198.38.109.0/24 |
dn: cn=config | |
objectClass: olcGlobal | |
cn: config | |
olcArgsFile: /home/matt/ldap/proxy/slapd.args | |
olcPidFile: /home/matt/ldap/proxy/slapd.pid | |
dn: cn=schema,cn=config | |
objectClass: olcSchemaConfig | |
cn: schema |
Once in a while, you may need to cleanup resources (containers, volumes, images, networks) ...
// see: https://github.com/chadoe/docker-cleanup-volumes
$ docker volume rm $(docker volume ls -qf dangling=true)
$ docker volume ls -qf dangling=true | xargs -r docker volume rm