Setting podManagementPolicy in Juju k8s StatefulSet

Bug #1834481 reported by Dominik Fleischmann on 2019-06-27
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Christian Muirhead

Bug Description

By default when deploying a Juju k8s charm with storage a StatefulSet is created where the Pods will be created if there are several units.

In a default StatefulSet the podManagementPolicy is set to OrderedReady so each pod will be created after the previous one is ready.

In Juju on the other hand this value has been changed to Parallel so all Pods are initiated at the same time.

This is causing us issues in some applications like a Mariadb Cluster where the Primary Node has to be created before the Secondary ones.

Adding an option, to make this value configurable in the Charms would solve these issues.

Tags: osm Edit Tag help
Richard Harding (rharding) wrote :

Tossing over to Christian to take a look at what we might need to do here. Thanks for the bug report.

Changed in juju:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Christian Muirhead (2-xtian)
Adam Israel (aisrael) on 2019-06-28
tags: added: osm
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers