1. Add a new relation to the openstack-integrator charm that looks like this:
provides:
loadbalancer:
interface: public-address
(Notice that this matches the loadbalancer relation provided by the kubeapi-load-balancer.)
2. Deploy CDK without the kubeapi-load-balancer, and instead relate the masters to the new loadbalancer relation on the openstack-integrator.
3. In the openstack-integrator, add handler code for the loadbalancer relation that will create a new Octavia LB that will balance across the k8s masters.
Proposal for how we could solve this:
1. Add a new relation to the openstack- integrator charm that looks like this:
provides:
loadbalancer:
interface: public-address
(Notice that this matches the loadbalancer relation provided by the kubeapi- load-balancer. )
2. Deploy CDK without the kubeapi- load-balancer, and instead relate the masters to the new loadbalancer relation on the openstack- integrator.
3. In the openstack- integrator, add handler code for the loadbalancer relation that will create a new Octavia LB that will balance across the k8s masters.
Is this an acceptable approach?