Kubernetes Control Plane Charm

kubernetes-master ignores changes to proxy-extra-args

Bug #1841112 reported by George Kraft
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kubernetes Control Plane Charm
Fix Released
Medium
Cory Johns
Kubernetes Control Plane Charm 1.19

Bug Description

I deployed cs:charmed-kubernetes-219. After the deployment settled, I ran:

juju config kubernetes-master proxy-extra-args="bind-address=0.0.0.0"

I expected this to reconfigure and restart kube-proxy on all of the kubernetes-master units with the new arg, but this didn't happen.

I confirmed by looking in /var/snap/kube-proxy/current/args that the new arg had not been set. It looks like kubernetes-master has no code to handle the config.changed.proxy-extra-args flag.

George Kraft (cynerva)
Changed in charm-kubernetes-master:
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
George Kraft (cynerva) wrote :

PR: https://github.com/charmed-kubernetes/charm-kubernetes-master/pull/99

Changed in charm-kubernetes-master:
assignee: nobody → Cory Johns (johnsca)
status: Triaged → In Progress
Tim Van Steenburgh (tvansteenburgh)
Changed in charm-kubernetes-master:
milestone: none → 1.19
Tim Van Steenburgh (tvansteenburgh)
Changed in charm-kubernetes-master:
status: In Progress → Fix Committed
Tim Van Steenburgh (tvansteenburgh)
Changed in charm-kubernetes-master:
status: Fix Committed → Fix Released
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.