The juju-autoscaler image seems locked to juju 2.9 controllers
Bug #2033320 reported by
Adam Dyess
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Kubernetes Autoscaler Charm |
Won't Fix
|
Low
|
Unassigned | ||
Bug Description
By the charm's own admission the oci-image sidecar used during deployment is rocks.canonical
While it may be possible to tweak this image to work for both 3.1 and 2.9 -- its not likely.
As of now -- juju autoscaling is locked to 2.9 controllers
| Changed in charm-kubernetes-autoscaler: | |
| milestone: | none → 1.29 |
Revision history for this message
| Adam Dyess (addyess) wrote | #1 |
| Changed in charm-kubernetes-autoscaler: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| milestone: | 1.29 → 1.30 |
| Changed in charm-kubernetes-autoscaler: | |
| milestone: | 1.30 → 1.31 |
Revision history for this message
| Adam Dyess (addyess) wrote | #2 |
| Changed in charm-kubernetes-autoscaler: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
The app can connect with the client to gather status, but fails when trying to add/remove units.
See here in this exception
E0829 14:15:47.117135 309371 scale_down.go:1144] Problem with empty node deletion: failed to delete juju-238b55-8: juju client with major version 2 used with a controller having major version 3 not supported
update your juju client to match the version running on the controller