Minikube MetalLB: Difference between revisions

From Chorke Wiki
Jump to navigation Jump to search
Line 53: Line 53:
spec:
spec:
   addresses:
   addresses:
   - 192.168.49.100-192.168.49.200
   - 192.168.49.100-192.168.49.199
---
---
apiVersion: metallb.io/v1beta1
apiVersion: metallb.io/v1beta1

Revision as of 14:24, 12 June 2025

helm repo add metallb https://metallb.github.io/metallb
helm repo update && helm repo list
kubectl config get-contexts

Config

export KUBECONFIG="${HOME}/.kube/dev-kubeconfig.yaml"
export KUBECONFIG="${HOME}/.kube/gcp-kubeconfig.yaml"
export KUBECONFIG="${HOME}/.kube/config"

Install

helm show values metallb/metallb --version=0.14.8|less
helm show values metallb/metallb --version=0.14.9|less


kubectl get ns|grep metallb-system
kubectl delete ns   metallb-system

kubectl get ns|grep metallb-system
kubectl create ns   metallb-system

cat <<YML | helm -n=metallb-system install    metallb metallb/metallb --version=0.14.9 -f=-
---
installCRDs: true
fullnameOverride: metallb
YML

cat << YML | kubectl -n=metallb-system apply -f=-
---
apiVersion: metallb.io/v1beta1
kind: IPAddressPool
metadata:
  name: metallb-ip-pool
  namespace: metallb-system
spec:
  addresses:
  - 192.168.49.100-192.168.49.199
---
apiVersion: metallb.io/v1beta1
kind: L2Advertisement
metadata:
  name: metallb-l2-ad
  namespace: metallb-system
spec:
  ipAddressPools:
  - metallb-ip-pool
YML

Uninstall

helm uninstall -n=metallb-system metallb
kubectl delete namespace metallb

MetalLB » Forward

Implement Forward Routing
Name Network Subnets Forward
Network » MetalLB 192.168.49.100/30 192.168.49.100 … 103/30 = 4
Network » MetalLB 192.168.49.104/30 192.168.49.104 … 107/24 = 4 ⚪️
Network » MetalLB 192.168.49.104/29 192.168.49.104 … 111/29 = 8
Network » MetalLB 192.168.49.112/29 192.168.49.112 … 119/29 = 8 ⚪️
Network » MetalLB 192.168.49.112/28 192.168.49.112 … 127/28 = 16
Network » MetalLB 192.168.49.128/28 192.168.49.128 … 143/28 = 16 ⚪️
Name Network Subnets Forward
Network » MetalLB 192.168.49.128/27 192.168.49.128 … 159/27 = 32
Network » MetalLB 192.168.49.160/27 192.168.49.160 … 191/27 = 32
Network » MetalLB 192.168.49.192/27 192.168.49.192 … 223/27 = 32 ⚪️
Network » MetalLB 192.168.49.192/29 192.168.49.192 … 199/29 = 8
Network » MetalLB 192.168.49.200/29 192.168.49.200 … 207/29 = 8 ⚪️
Network » MetalLB 192.168.49.208/29 192.168.49.208 … 215/29 = 8 ⚪️

Playground

kubectl get pods -n metallb-system -o=yaml|yq -r .items[].spec.containers[].image|awk -F @ '{printf("%s\n", $1)}'|sort -h

kubectl -n=metallb-system logs -f svc/metallb-webhook-service -c=controller
kubectl -n=metallb-system logs -f svc/metallb-webhook-service

kubectl -n=metallb-system describe L2Advertisement metallb-l2-ad
kubectl -n=metallb-system get L2Advertisement

kubectl -n=metallb-system describe IPAddressPool metallb-ip-pool
kubectl -n=metallb-system get IPAddressPool

docker network prune -f
docker volume  prune -f
docker system  prune -f
docker image ls
cat <<'EXE' | bash
for d in system network volume
do docker ${d} prune -f;done
EXE
cat <<'EXE' | ssh deploy@ci.chorke.org
for d in system network volume
do docker ${d} prune -f;done
EXE

systemctl stop    minikube.service
systemctl status  minikube.service
systemctl restart minikube.service
systemctl stop    minikube-tunnel.service
systemctl status  minikube-tunnel.service
systemctl restart minikube-tunnel.service
systemctl status network-online.target
systemctl status containerd.service
systemctl status docker.service

minikube addons disable metallb
minikube addons enable  metallb
minikube addons list
minikube status
sudo journalctl -xeu minikube-tunnel
sudo journalctl -xeu minikube
sudo -i -u minikube
minikube ssh

References