JeffYang

Hi @KingDaemonX If you addressed something, you can resolve the related comments.

I notice this PR #2451 introduce a new annotation `loadbalancer.openstack.org/floating-ip`, I like this change. But, It seems like similar with `service.beta.kubernetes.io/openstack-internal-load-balancer` in semantics. IMO, If a LB has FloatingIP it...

@zetaab I agree with you, I also think there are not many service.beta.kubernetes.io annotations. I just think the annotation `service.beta.kubernetes.io/openstack-internal-load-balancer` will become redundant after we introduce `loadbalancer.openstack.org/floating-ip`. Service has floating-ip...

Thanks @zetaab @dulek. I got it. > Current code doing internal LBs is super complicated already due to shared LBs. I really agree that.

> I think CPO expects CAPO or other deployment tool to manage this. Why can't it be done there? As I mentioned [here](https://github.com/kubernetes/cloud-provider-openstack/pull/2484#issuecomment-1831013648), This is route controller's duty to ensure...

> @jeffyjf are you sure that the problem lies in node's security groups? Yep, I'm sure. I've already done test, add extra node's security group can deal with this issue....

Hi, Is anyone still working on this issue. @kayrus If you haven't started this work, could you leave it to me? I think that we should introduce finalizer to resolve...

Hi @mdbooth We all agree that if a volume created from a snapshot, the snapshot shouldn't be deleted before the volume, right? But, I haven't understood the sentence: > Or...

> Why did this ended up in Routes controller? The issue description feels like this is a general issue in cases CAPO is missing SG rules to allow interconnectivity of...

@dulek @jichenjc @kayrus @zetaab asking for review