Yunkang Ren

Besides this "no avliable eip" error, is there any other error message?

> Could this be caused by Calico v3.24.5? should not be. Could you show more logs of `openelb-manager`

`eip` is not ready. It should be that your interface does not allow `openelb-manager` to listen arp package, so it cannot create a speaker.

It is caused by container securityContext. You can modify the securityContext of openelb-manager as shown below: ``` securityContext: capabilities: add: - NET_ADMIN - SYS_TIME - NET_RAW - NET_BIND_SERVICE ``` more...

> > It is caused by container securityContext. You can modify the securityContext of openelb-manager as shown below: > > ``` > > securityContext: > > capabilities: > > add:...

There may be such a problem. Let me tell you why. If your cluster has 2 nodes, A and B. When using layer2 mode, we will use round robin to...

If you only want to use layer2 mode, maybe we can solve it in the following way. Assign eip to specific nodes, https://github.com/openelb/openelb/issues/310, and make sure that there is a...

It same as https://github.com/openelb/openelb/issues/151, Due to some factors, we have not supported it yet, we will support it in a later iteration

We haven't implemented such a feature yet. We can implement it as a new feature later.

There are some updates, you can try the new version. The download timeout may be caused by some special characters in the file name or other reasons.