kubernetes-master unit removal can be very slow

Bug #1821967 reported by George Kraft
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kubernetes Control Plane Charm
Fix Released
Undecided
Joseph Borg

Bug Description

Issue observed during testing for CDK 1.14.

Test timed out because a kubernetes-master unit took over 40 minutes to remove. The flannel/3 unit had been removed from kubernetes-master/1, but kubernetes-master/1 was still running the configure_cdk_addons handler. With flannel no longer running, kube-apiserver was no longer able to reach the metrics-server pod, and this caused kubectl commands to take a very long time.

Revision history for this message
George Kraft (cynerva) wrote :
Revision history for this message
Joseph Borg (joeborg) wrote :
Changed in charm-kubernetes-master:
assignee: nobody → Joseph Borg (joeborg)
status: New → Fix Committed
Changed in charm-kubernetes-master:
milestone: none → 1.16
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.

Other bug subscribers

Remote bug watches

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