some ip within metallb-system suddently does not work
arp -a
arping ip_address
iptables -L -n
ip route get 192.168.1.88
sudo ip neigh flush all
kubectl -n metallb-system rollout restart deployment controller
kubectl -n metallb-system rollout restart deployment speaker
kubectl -n metallb-system logs -l component=speaker
kubectl -n metallb-system get daemonset
kubectl -n metallb-system get all
iptables -F
iptables -X
iptables -t nat -F
iptables -t nat -X
iptables -t mangle -F
iptables -t mangle -X
iptables -t raw -F
iptables -t raw -X
iptables -t security -F
iptables -t security -X
iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT
all does not work
until updated to:
kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.14.9/config/manifests/metallb-native.yaml
kubectl apply -f metallb-config.yaml
Another trouble shooting:
kubectl describe svc service_name
NodePort: <unset> 32067/TCP
Endpoints: <none> <—- this should have something otherwise means
No, the empty Endpoints (<none>) indicate that your service is not correctly routing traffic to the pods. This means that either:
- No pods match the selector (
app=your_app, tier=frontend), or - The pods are not in a “Ready” state, or
- The pods are not listening on the expected port (80).
In this case svc’s selector did not match pod’s label. after fix , it is working
