The enable-<cloud> flags should not be set until external provider support is added

Bug #1842125 reported by Cory Johns
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kubernetes Control Plane Charm
Fix Released
Undecided
Cory Johns

Bug Description

In order to ensure that the transition from the in-tree provider to the external provider for each cloud is seamless, the k8s-master charm should hold off on setting the enable-<cloud> flag for each cloud until it has support for that cloud's external provider. This way, the support in cdk-addons can be done and backported when available, and it will continue to work with older charms which don't support the external provider, since those charms will not set the relevant enable flag.

Revision history for this message
Cory Johns (johnsca) wrote :
Changed in charm-kubernetes-master:
assignee: nobody → Cory Johns (johnsca)
status: New → Fix Committed
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.