there is a chance the http relation is configuring services twice as "target_service"

Hello,

Problem:

When relating the kubernetes-workers and masters to the load-balancer the services are being configured twice as "target_service".

Detail:

As a result is nginx will fail to start and the hacluster will show a failed resource with the nginx config looking like this:

# /etc/nginx/sites-enabled/apilb
upstream target_service {
  server 172.25.94.125:6443;
  server 172.25.94.126:6443;

}
upstream target_service {
  server 172.25.94.125:9103;
  server 172.25.94.126:9103;
  server 172.25.94.127:9103;
  server 172.25.94.128:9103;
  server 172.25.94.129:9103;
  server 172.25.94.130:9103;
  server 172.25.94.131:9103;
  server 172.25.94.132:9103;
  server 172.25.94.133:9103;
  server 172.25.94.134:9103;

}

Workaround:

Remove relations:

- kubeapi-load-balancer:loadbalancer kubernetes-master:loadbalancer
- kubeapi-load-balancer:apiserver kubernetes-master:kube-api-endpoint
- kubernetes-worker kubeapi-load-balancer

Wait for all three relations to be removed, then re-add the relations.

The file should come back without the duplicate entry.

Cheers,

Peter