kubernetes master cannot cluster with itself across CMR

Bug #1951316 reported by Jeff Hillman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kubernetes Control Plane Charm
New
Undecided
Unassigned

Bug Description

juju 2.9.18
k8s 1.22
openstack ussuri
ubuntu focal

In the event of attempting to stretch the kubernetes control plane across multiple openstack regions, kubernetes master cannot relate to itself neither via the coordinator nor kube-masters endpoints.

Steps to recreate:

```
On RegionOne

$ juju add-model r1

### deploy k8s master and offer relevant endpoints for CMR

$ juju deploy cs:~containers/kubernetes-master --constraints instance-type=4-4-16
$ juju offer kubernetes-master:coordinator k8s-master-coordinator
$ juju offer kubernetes-master:kube-masters k8s-master-kube-masters

$ juju add-model r2

### deploy k8s master and attempt to consume offers from r1

$ juju deploy cs:~containers/kubernetes-master --constraints instance-type=4-4-16

### attempt k8s master offers

$ juju add-relation kubernetes-master:coordinator r1:admin/r1.k8s-master-coordinator
ERROR no relations found

$ juju add-relation kubernetes-master:coordinator r1:admin/r1.k8s-master-kube-masters
ERROR no relations found

```

Easyrsa can be offered/consume just fine with the same scenario.

This inhibits the ability to span the control plane across openstack regions/cloud for maximum high-availability

Tags: cpe-onsite
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.