[occm] VIP of the LB can be specified during creation

[syy6]

[occm] VIP of the LB can be specified during creation

[kayrus]

@syy6 FIP cannot be set globally unlike the network-id and subnet-id. FIP should be set with a service spec: Spec.LoadBalancerIP. However this is being changing in the #2451 PR with a new loadbalancer.openstack.org/floating-ip annotation label.

[yang-wang11]

From my perspective, the term "VIP" (Virtual IP) in this context refers to a private IP address.
PR #2451 was specifically tailored for public IP addresses, commonly known as floating IPs. Therefore, it falls outside the purview of PR #2451.

@kayrus
I skimmed the code, and I found the annotation loadbalancer.openstack.org/load-balancer-address is just a result and cannot be assigned(it will not work), this annotation can probably be reused(like loadbalancer.openstack.org/network-id and loadbalancer.openstack.org/subnet-id) for the private LB case, or maybe introduce a new annotation

[kayrus]

@yang-wang11 indeed, I mixed up FIP and VIP. For VIP you have to use loadbalancer.openstack.org/port-id, which, unfortunately, is not in an IP format.

[dulek]

You can also try playing with internal services:

cloud-provider-openstack/pkg/openstack/loadbalancer.go

Lines 260 to 264 in 9e7794b

	// For external load balancer, the LoadBalancerIP is a public IP address.
	loadBalancerIP := service.Spec.LoadBalancerIP
	if loadBalancerIP != "" && svcConf.internal {
	createOpts.VipAddress = loadBalancerIP
	}

[syy6]

Thanks @dulek , I just tested and it works!