[Master/Worker/CMR - RFE] Update validation scripts to accept worker and master nodes on different models

Bug #1864467 reported by Pedro Guimarães
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Charmed Kubernetes Testing
Triaged
Wishlist
Unassigned

Bug Description

We generally deploy Charmed Kubernetes with all-integrated k8s masters and workers. This means, for example, on a cloud network, master and worker nodes will be placed in the same network.

However, it makes sense to have different networks for masters and workers and free operators to enforce different firewall and routing rules to those networks.

One solution would be to use spaces and have different spaces per-application. But not all Juju providers offer space concept, such as vsphere or openstack.

An alternative is to create k8s masters and workers on different Juju models and relate them through CMR.

That allows operators to select which networks each node will come up and enforce different policies for each.

To achieve a complete Charmed Kubernetes deployment using master/worker CMR, however, validation scripts need to be adapted. They need to take into consideration that a second model only for workers may be present on this deployment and offer the corret options for that.

Revision history for this message
George Kraft (cynerva) wrote :

I'm assuming you're talking about the validation tests in our testing repo, and have adjusted the projects on this issue accordingly. Please let me know if I misunderstood.

no longer affects: charm-kubernetes-master
no longer affects: charm-kubernetes-worker
Changed in charmed-kubernetes-testing:
status: New → Confirmed
George Kraft (cynerva)
Changed in charmed-kubernetes-testing:
importance: Undecided → Wishlist
status: Confirmed → Triaged
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.