I tested a workaround by changing the daemonset "kubectl edit daemonset -n kube-system openstack-cloud-controller-manager" to use the correct cluster name:
1001 345683 345576 9 20:44 ? 00:00:01 /bin/openstack-cloud-controller-manager --cluster-name=kubernetes-fu6ks9empuz38g7utkc1n6unudbn9dc1 --v=1 --cluster-name=kubernetes-fu6ks9empuz38g7utkc1n6unudbn9dc1 --cloud-config=/etc/config/cloud.conf --cloud-provider=openstack --use-service-account-credentials=true --bind-address=127.0.0.1
With this, the LB is created with the right name:
| 03f1a0e3-68cf-45da-ab76-10c45b5f01e4 | kube_service_kubernetes-fu6ks9empuz38g7utkc1n6unudbn9dc1_default_microbot-service-test | f98f4210a9764fff93ed4bd58b710025 | 10.6.1.117 | PENDING_CREATE | OFFLINE | amphora |
I tested a workaround by changing the daemonset "kubectl edit daemonset -n kube-system openstack- cloud-controlle r-manager" to use the correct cluster name:
1001 345683 345576 9 20:44 ? 00:00:01 /bin/openstack- cloud-controlle r-manager --cluster- name=kubernetes -fu6ks9empuz38g 7utkc1n6unudbn9 dc1 --v=1 --cluster- name=kubernetes -fu6ks9empuz38g 7utkc1n6unudbn9 dc1 --cloud- config= /etc/config/ cloud.conf --cloud- provider= openstack --use-service- account- credentials= true --bind- address= 127.0.0. 1
With this, the LB is created with the right name:
| 03f1a0e3- 68cf-45da- ab76-10c45b5f01 e4 | kube_service_ kubernetes- fu6ks9empuz38g7 utkc1n6unudbn9d c1_default_ microbot- service- test | f98f4210a9764ff f93ed4bd58b7100 25 | 10.6.1.117 | PENDING_CREATE | OFFLINE | amphora |