We assume ControlPlaneEndpoint.Host is IP address

[mdbooth]

/kind bug

From code inspection, we set fixedIPAddress to ControlPlaneEndpoint.Host if not using APIServer FloatingIP:

cluster-api-provider-openstack/pkg/cloud/services/loadbalancer/loadbalancer.go

Lines 54 to 59 in 62d9d76

	switch {
	case openStackCluster.Spec.APIServerFixedIP != "":
	fixedIPAddress = openStackCluster.Spec.APIServerFixedIP
	case openStackCluster.Spec.DisableAPIServerFloatingIP && openStackCluster.Spec.ControlPlaneEndpoint.IsValid():
	fixedIPAddress = openStackCluster.Spec.ControlPlaneEndpoint.Host
	}

We then pass that to getOrCreateLoadBalancer, which expects it to be a VipAddress:

cluster-api-provider-openstack/pkg/cloud/services/loadbalancer/loadbalancer.go

Lines 174 to 182 in 62d9d76

	lbCreateOpts := loadbalancers.CreateOpts{
	Name: loadBalancerName,
	VipSubnetID: subnetID,
	VipAddress: vipAddress,
	Description: names.GetDescription(clusterName),
	Provider: provider,
	Tags: openStackCluster.Spec.Tags,
	}
	lb, err = s.loadbalancerClient.CreateLoadBalancer(lbCreateOpts)

However, ControlPlaneEndpoint.Host is not required to be an IP address. It may be a DNS name.

Same when creating the load balancer FIP:

cluster-api-provider-openstack/pkg/cloud/services/loadbalancer/loadbalancer.go

Lines 92 to 97 in 62d9d76

	switch {
	case openStackCluster.Spec.APIServerFloatingIP != "":
	floatingIPAddress = openStackCluster.Spec.APIServerFloatingIP
	case openStackCluster.Spec.ControlPlaneEndpoint.IsValid():
	floatingIPAddress = openStackCluster.Spec.ControlPlaneEndpoint.Host
	}

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale