Canonical Juju

HA Juju controller on Kubernetes

Bug #1869211 reported by Tytus Kurek
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Low
Unassigned

Bug Description

At the moment it is not possible to deploy a highly available Juju controller on Kubernetes. This makes Juju a single point of failure in K8s scenarios and significantly impacts its resiliency. A solution for that would be a highly available Juju controller on Kubernetes with anti-affinity.

Ian Booth (wallyworld)
Changed in juju:
milestone: none → 2.9-beta1
importance: Undecided → High
status: New → Triaged
Ian Booth (wallyworld)
tags: added: k8s
Canonical Juju QA Bot (juju-qa-bot)
Changed in juju:
milestone: 2.9-beta1 → 2.9-rc1
Revision history for this message
John A Meinel (jameinel) wrote :

This was explicitly taken off feature priority for this cycle as you can still use an LXD controller if you must have HA

Changed in juju:
milestone: 2.9-rc1 → none
Pen Gale (pengale)
Changed in juju:
importance: High → Medium
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: Medium → Low
tags: added: expirebugs-bot
Revision history for this message
Bartłomiej Poniecki-Klotz (barteus) wrote (last edit ):

We see more interest from the end users in the K8s cluster bootstrapped JUJU. In some environments, there are no additional VMs to bootstrap into for the HA juju controller.

Can we put it in future roadmaps?

Revision history for this message
Camille Rodriguez (camille.rodriguez) wrote :

+1 @bartlomiej - this feature is necessary for the application deployments that we do in kubernetes, becoming more and more common nowadays

Revision history for this message
James Page (james-page) wrote :

I'd also like to move to using K8S hosted Juju controllers for OpenStack Sunbeam.

This would significantly reduce the complexity of operations such as major or minor juju upgrades (which now require model migrations to a controller of the target version) - creating a new controller under K8S and then migrating models to it should be very repeatable/reliable and would avoid the use of another technology in sunbeam (LXD) to deal with multiple controller installations on the same set of machines in order to support upgrades.

Would love to see this feature bumped in priority :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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