Yunkang Ren

> If you set the external-ip of the LoadBalancer Service, the Kube-Proxy will modify iptables or ipvs rules on all Nodes. This is very dangerous because it disturbes the cluster...

It is not recommended that you modify it this way. This breaks the working principle of openelb layer2 mode. Your modification will refresh all existing allocations to the mac of...

For the version of `openelb` you are using, you may consider increasing the number of replicas of `openelb-manager`. Modify the scheduling rules so that it can be dispatched to different...

```yaml apiVersion: v1 kind: ConfigMap metadata: name: openelb-images namespace: openelb-system data: keepalived-vip-image: kubesphere/kube-keepalived-vip:0.35 ``` 1. Please confirm whether the configuration of configmap is correct. 2. The configmap should be in...

可以使用bird，首先你需要保证两台服务器四层可达，之后你再去验证是否建立了 bgppeer 以及是否收到对应的路由

According to your description, I did not reproduce it, can you describe it in more detail? 

According to your description, I tried it again, but I still can't reproduce the problem. You can check to see if it's caused by other factors.

`eip.openelb.kubesphere.io/v1alpha1` is similar to `svc.Spec.LoadBalancerIP` for specifying svc ip. `eip.openelb.kubesphere.io/v1alpha2` is the eip pool designated for assigning ip addresses. Here you can delete annotation `eip.openelb.kubesphere.io/v1alpha1`.

1. Please make sure other hosts and the cluster are in the same network segment 2. 4881 is the nodeport, so you should access 192.168.212.70:9090

Is this issue the same use case as this one? https://github.com/openelb/openelb/issues/323