Comment 3 for bug 1896542

We saw this again in https://solutions.qa.canonical.com/testruns/testRun/96f7e6de-6de6-40f9-884d-65bbef1f749f and https://solutions.qa.canonical.com/v2/testruns/24b447e7-a677-4820-85d3-95d9b0a4d88e. Now we do relate kubeapi-load-balancer with:

- ['filebeat:beats-host', 'kubeapi-load-balancer:juju-info']
- ['hacluster-kubeapi-load-balancer:ha', 'kubeapi-load-balancer:ha']
- ['hacluster-kubeapi-load-balancer:nrpe-external-master', 'nrpe:nrpe-external-master']
- ['kubeapi-load-balancer:apiserver', 'kubernetes-control-plane:kube-api-endpoint']
- ['kubeapi-load-balancer:certificates', 'vault:certificates']
- ['kubeapi-load-balancer:juju-info', 'nrpe:general-info']
- ['kubeapi-load-balancer:juju-info', 'telegraf:juju-info']
- ['kubeapi-load-balancer:loadbalancer', 'kubernetes-control-plane:loadbalancer']
- ['kubeapi-load-balancer:nrpe-external-master', 'nrpe:nrpe-external-master']
- ['kubeapi-load-balancer:website', 'kubernetes-worker:kube-api-endpoint']

Can we investigate this?