Lubron

The create and delete permission shouldn't be needed.

/lgtm /approve

Sorry. I'll take a look at the code. Currently, workaround would be using below configuration to exclude the floating IP ``` [Nodes] exclude-internal-network-subnet-cidr exclude-external-network-subnet-cidr ```

Are you passing `--node-ip` to your kubelet? https://github.com/kubernetes/cloud-provider/blob/v0.22.6/controllers/node/node_controller.go#L695-L708 Looks like if the IP that vsphere CPI pick up doesn't match the kubelet ip then it will fail. Let me check...

We removed the service from CPI, let me fix the helm

It's fixed in 1.24.1

As suggested by @sedefsavas, changing the target group type from instance to IP, can also workaround this issue https://aws.amazon.com/premiumsupport/knowledge-center/target-connection-fails-load-balancer/ But the downside of this is the IP of instance might...

Thanks @artembilan Is there any plan to add this renewLock to this part of logic? https://github.com/spring-projects/spring-integration/blob/master/spring-integration-core/src/main/java/org/springframework/integration/support/leader/LockRegistryLeaderInitiator.java#L400-L408 Or we have to wait for modification on other `LockRegistry` first?

Oh just saw your PR. could you help update go version in these two files as well? https://github.com/kubernetes/cloud-provider-vsphere/blob/master/cluster/images/controller-manager/Dockerfile https://github.com/kubernetes/cloud-provider-vsphere/blob/master/hack/images/ci/Dockerfile#L6

/lgtm /approve Thank you!