jv
/
my-homelab-configs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: scale down website replicas and adjust anti-affinity rules

This commit is contained in:
jv 2026-05-19 16:10:27 -05:00
parent ed46acc154
commit a256bd02bd
1 changed files with 18 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
lab.sh
View File

@ -60,7 +60,7 @@ nuke() {
sudo umount /var/lib/containerd/srun/* 2>/dev/null || true sudo umount /var/lib/containerd/srun/* 2>/dev/null || true
sudo rm -rf /var/lib/containerd/* /run/containerd/* sudo rm -rf /var/lib/containerd/* /run/containerd/*
sudo rm -rf /etc/kubernetes/ /var/lib/etcd/ /var/lib/kubelet/ /var/lib/cni/ /etc/cni/net.d /home/jv/.kube/ sudo rm -rf /etc/kubernetes/ /var/lib/kubelet/ /var/lib/cni/ /etc/cni/net.d /home/jv/.kube/
sudo iptables -F && sudo iptables -t nat -F && sudo iptables -t mangle -F && sudo iptables -X sudo iptables -F && sudo iptables -t nat -F && sudo iptables -t mangle -F && sudo iptables -X
sudo ip link delete cilium_host 2>/dev/null || true sudo ip link delete cilium_host 2>/dev/null || true
@ -71,10 +71,25 @@ nuke() {
echo "--> Eviscerating remote Kubernetes components (Raspberry Pi)..." echo "--> Eviscerating remote Kubernetes components (Raspberry Pi)..."
ssh -o ConnectTimeout=5 jv@192.168.100.89 << 'EOF' 2>/dev/null || true ssh -o ConnectTimeout=5 jv@192.168.100.89 << 'EOF' 2>/dev/null || true
sudo kubeadm reset --force # 1. Force reset kubeadm configurations
sudo kubeadm reset --force || true
# 2. Halt the container runtime engine to drop file descriptor and socket locks
sudo systemctl stop containerd 2>/dev/null || true
sudo killall containerd-shim-runc-v2 2>/dev/null || true sudo killall containerd-shim-runc-v2 2>/dev/null || true
sudo rm -rf /var/lib/kubelet/ /var/lib/cni/ /etc/cni/net.d /var/lib/containerd/*
# 3. Unmount any lingering ephemeral pod volumes, secrets, or token rings
sudo umount -f /var/lib/kubelet/pods/*/*/*/* 2>/dev/null || true
# 4. Completely wipe the cluster file configurations and runtime data tracks
sudo rm -rf /etc/kubernetes/ /var/lib/kubelet/ /var/lib/cni/ /etc/cni/net.d
sudo rm -rf /var/lib/containerd/* /run/containerd/*
# 5. Reset network routing policies left over by the CNI
sudo iptables -F && sudo iptables -t nat -F && sudo iptables -t mangle -F && sudo iptables -X sudo iptables -F && sudo iptables -t nat -F && sudo iptables -t mangle -F && sudo iptables -X
# 6. Bring the container engine back online with a completely clean state slate
sudo systemctl start containerd
EOF EOF
docker buildx rm lab-builder 2>/dev/null || true docker buildx rm lab-builder 2>/dev/null || true