So basically, replacing the above 2 relations to the following 3 relations will allow to deploy kubeapi-load-balancer kubernetes-control-plane on the same host.
But I believe the `kube-api-endpoint` relations is kind of deprecated and as far as I see from the ops branch in kuberenetes-control-plane, this relation is been removed.
I believe it worked with the relations that we used to have before
- ['kubernetes- control- plane:loadbalan cer-external' , 'kubeapi- load-balancer: lb-consumers' ] control- plane:loadbalan cer-internal' , 'kubeapi- load-balancer: lb-consumers' ]
- ['kubernetes-
According to https:/ /github. com/charmed- kubernetes/ bundle, I believe 1.21 is the last bundle that used the previous relations.
https:/ /github. com/charmed- kubernetes/ bundle/ blob/main/ releases/ 1.21/bundle. yaml
So basically, replacing the above 2 relations to the following 3 relations will allow to deploy kubeapi- load-balancer kubernetes- control- plane on the same host.
- ['kubeapi- load-balancer: apiserver' , 'kubernetes- control- plane:kube- api-endpoint' ] load-balancer: loadbalancer' , 'kubernetes- control- plane:loadbalan cer'] load-balancer: website' , 'kubernetes- worker: kube-api- endpoint' ]
- ['kubeapi-
- ['kubeapi-
But I believe the `kube-api-endpoint` relations is kind of deprecated and as far as I see from the ops branch in kuberenetes- control- plane, this relation is been removed.