openeuler/keepalived 运行 VRRP 协议守护进程，通过 master/backup 选举将 VIP 绑定到健康节点，常用于物理机或裸金属入口层高可用。容器化部署通常需要 --cap-add=NET_ADMIN、--network host 或 macvlan，不适合常规 Kubernetes Deployment（无 hostNetwork 时无法接管 VIP）。生产 K8s 场景应使用 MetalLB、kube-vip 或云 LB 替代容器内 keepalived。

快速启动

docker run -d --name keepalived \
  --network host --cap-add=NET_ADMIN \
  -v $(pwd)/keepalived.conf:/etc/keepalived/keepalived.conf:ro \
  docker.io/openeuler/keepalived:latest

推荐实践

docker run -d --name keepalived \
  --restart unless-stopped \
  --network host --cap-add=NET_ADMIN --cap-add=NET_RAW \
  -v /etc/keepalived/keepalived.conf:/etc/keepalived/keepalived.conf:ro \
  -e KEEPALIVED_INTERFACE=eth0 \
  docker.io/openeuler/keepalived:2.2.8

核心参数说明

• --network host — VIP 需绑定宿主机网卡
• --cap-add=NET_ADMIN — 允许配置 IP 与路由
• -v .../keepalived.conf:...:ro — VRRP 实例与 VIP 定义
• -e KEEPALIVED_INTERFACE — 绑定网卡名称
• --restart unless-stopped — 守护进程异常自动恢复
• K8s — 常规 Pod 无法满足 VIP 漂移需求