2、MetalLB_metallb ip池可以是宿主机ip吗?-CSDN博客

本文详细介绍了如何在k8s集群的master节点上安装和配置MetalLB，包括设置kube-proxy的strictARP模式，启用L2模式以及创建并管理IP地址池，以实现在kubernetes环境中使用EXTERNAL-IP的负载均衡功能。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

2、MetalLB

使用 MetalLB 让 LoadBalancer 服务使用 EXTERNAL-IP

在 k8s-master 安装 MetalLB

https://github.com/metallb/metallb

https://metallb.universe.tf/installation/

kubectl get configmap -n kube-system kube-proxy
apiVersion: kubeproxy.config.k8s.io/v1alpha1
kind: KubeProxyConfiguration
mode: "ipvs"
ipvs:
  strictARP: true

# see what changes would be made, returns nonzero returncode if different
kubectl get configmap kube-proxy -n kube-system -o yaml | \
sed -e "s/strictARP: false/strictARP: true/" | \
kubectl diff -f - -n kube-system

# actually apply the changes, returns nonzero returncode on errors only
kubectl get configmap kube-proxy -n kube-system -o yaml | \
sed -e "s/strictARP: false/strictARP: true/" | \
kubectl apply -f - -n kube-system

kubectl rollout restart daemonset kube-proxy -n kube-system

配置 MetalLB 为Layer2 模式

# kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.13.12/config/manifests/metallb-native.yaml

mkdir -p ~/MetalLB-yml && cd ~/MetalLB-yml

wget https://raw.githubusercontent.com/metallb/metallb/v0.13.12/config/manifests/metallb-native.yaml

kubectl apply -f ~/MetalLB-yml/metallb-native.yaml

# k8s-master 创建ip地址池
cat > ~/MetalLB-yml/iptool.yaml << 'EOF'
apiVersion: metallb.io/v1beta1
kind: IPAddressPool
metadata:
  name: default
  namespace: metallb-system
spec:
  addresses:
  - 192.168.1.100-192.168.1.119 # 网段跟node节点保持一致
  autoAssign: true
---
apiVersion: metallb.io/v1beta1
kind: L2Advertisement
metadata:
  name: default
  namespace: metallb-system
spec:
  ipAddressPools:
  - default
EOF

kubectl apply -f ~/MetalLB-yml/iptool.yaml

# kubectl get IPAddressPool -n metallb-system
NAME      AUTO ASSIGN   AVOID BUGGY IPS   ADDRESSES
default   true          false             ["192.168.1.100-192.168.1.119"]