Unable to force autoscaler to be scheduled on control-plane-node via Juju

Bug #1971453 reported by Stone Preston
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kubernetes Autoscaler Charm
Triaged
Low
Unassigned

Bug Description

Juju is currently unable to force the autoscaler charm to be scheduled on a control-plane node. https://bugs.launchpad.net/juju/+bug/1970991 currently tracks this issue. The Juju team has this feature on their 22.10 roadmap.

As a workaround, the autoscaler charm can be rescheduled on a control plane node after deployment using the following kubectl command:

kubectl patch statefulset kubernetes-autoscaler -p '{"spec": {"template": {"spec": {"nodeSelector": {"juju-application": "kubernetes-control-plane"}}}}}' -n autoscaler-model

Adam Dyess (addyess)
Changed in charm-kubernetes-autoscaler:
milestone: none → 1.29
Changed in charm-kubernetes-autoscaler:
status: New → Triaged
importance: Undecided → Low
milestone: 1.29 → 1.30
Adam Dyess (addyess)
Changed in charm-kubernetes-autoscaler:
milestone: 1.30 → 1.31
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.