> doing an `openstack loadbalancer show <uuid>` doesn't show a FIP. However, the kubeconfig provided by k8s-master has a FIP.
This is expected. `loadbalancer show` outputs a vip of the loadbalancer and it's usually on a private network, and the vip will be associated with an floating IP for external access.
> doing an `openstack loadbalancer show <uuid>` doesn't show a FIP. However, the kubeconfig provided by k8s-master has a FIP.
This is expected. `loadbalancer show` outputs a vip of the loadbalancer and it's usually on a private network, and the vip will be associated with an floating IP for external access.
One thing I noticed when I was testing it was that the floating IP network must be specified before deploying and relating openstack- integrator with k8s-master. Looks like the config is used only when creating the loadbalancer. /github. com/juju- solutions/ charm-openstack -integrator/ blob/244b8d533f 38f18fc6908dc8f 9327c9b767a47cc /lib/charms/ layer/openstack .py#L149- L163
https:/