Bassem Tadros

@embik unfortunately this didn't fix the issue stated in https://github.com/kubermatic/kubermatic/issues/12905

Hi @embik ,you can see below in the preset the external network is **named external**, while in the cluster object it annotates the floating ip pool id of the the...

@embik yes correct, the name in the CRDs are the same, unfortunately i can not delete clusters.management.cattle.io as this will break the rancher cluster. I guess you will have the...

Hi @embik, yes i agree that this error is coming from the openstack side, outside of kkp the openstack provider is working correctly provisioning Lbs and attaching floating IPs. Yes...

@embik Hi Marvin, regarding your questions 1- the same configuration works on the underlying rancher cluster and LBs are being provisioned correctly 2- when trying without provider presets and doing...

I think this should be exposed in the presets https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/openstack-cloud-controller-manager/using-openstack-cloud-controller-manager.md floating-network-id Optional. The external network used to create floating IP for the load balancer VIP. **If there are multiple external...

> Please format config files and logs that you are sharing with tree backticks before and after (known as "code blocks"). @embik Done, kindly check

@embik yes this successfully provisioned the LB as shown below once adding the annotation ``` [bassem@ssh-proxy ~]$ kubectl apply -f test.yaml deployment.apps/test-deployment created service/apache-service created ``` [bassem@ssh-proxy ~]$ kubectl get...