Yunkang Ren
Yunkang Ren
**Describe the Bug** Missing openelb annotation hint when creating service of type loadbalancer.  It should be like this:  **Versions Used** KubeSphere: 3.3.0
**Describe the Bug** Use openelb as service loadbalancer, should check whether openelb has been installed.  **Versions Used** KubeSphere: v3.3.0 /kind bug
Signed-off-by: renyunkang ## Description **What type of PR is this ?:** 1. Using vip mode will create a configmap in advance to avoid finding the corresponding configmap all the time...
### What we need In the case of using openelb as the Kubernetes load balancing implementation, the allocation of openelb external-ip-pool can only be viewed on the terminal interface by...
When the eip configured in layer2 or vip mode and the specified NIC are not in the same network segment, an error should be reported instead of being created successfully....
When concurrently deleting eip and service that exposed loadbalancer type using openelb, ip cannot be recycled. /kind bug
**Describe the Bug** Install kubesphere and enable devops using kubekey in ksv environment, the installation fails.  here is logs: ``` Task 'devops' failed: ****************************************************************************************************************************************************** { "counter": 131, "created": "2022-06-13T06:44:55.053304",...
## Description **What type of PR is this ?:** fix: keepalive speaker clear datas when stopped ## Related links:
**Is your feature request related to a problem? Please describe.** https://github.com/openelb/openelb/discussions/397 **Describe the solution you'd like** **Describe alternatives you've considered** **Additional context**