configure kubelet when ext cloud provider changes

Bug #2015132 reported by Kevin W Monroe
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kubernetes Control Plane Charm
Fix Released
High
Kevin W Monroe
Kubernetes Worker Charm
Fix Released
High
Kevin W Monroe

Bug Description

According to the reactive docs[0], we should be reacting to `endpoint.{ep}.changed.{field}`. This could cause problems wherein kubelets are not started with the `external` cloud-provider argument, which could lead to incorrect node init depending on the cloud provider.

0: https://charmsreactive.readthedocs.io/en/latest/charms.reactive.relations.html#charms.reactive.endpoints.Endpoint

Revision history for this message
Kevin W Monroe (kwmonroe) wrote (last edit ):
Changed in charm-kubernetes-worker:
milestone: none → 1.27
assignee: nobody → Kevin W Monroe (kwmonroe)
importance: Undecided → High
status: New → In Progress
Revision history for this message
Kevin W Monroe (kwmonroe) wrote :
summary: - incorrect endpoint flag name for has-xcp
+ configure kubelet when ext cloud provider changes
Changed in charm-kubernetes-master:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Kevin W Monroe (kwmonroe)
milestone: none → 1.27
Changed in charm-kubernetes-master:
status: In Progress → Fix Committed
Changed in charm-kubernetes-worker:
status: In Progress → Fix Committed
Changed in charm-kubernetes-master:
status: Fix Committed → Fix Released
Changed in charm-kubernetes-worker:
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.