Switch to external OpenStack cloud provider and auto-create storage classes

Bug #1837747 reported by Cory Johns
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
CDK Addons
Fix Released
Wishlist
Cory Johns
Kubernetes Control Plane Charm
Fix Released
Wishlist
Cory Johns
Kubernetes Worker Charm
Fix Released
Wishlist
Cory Johns

Bug Description

The cloud provider components are being moved out of the core Kubernetes code tree and being implemented as in-cluster plugins, with OpenStack being the first to have been converted. Additionally, when integration is enabled we should create a reasonable default storage class automatically.

Revision history for this message
Cory Johns (johnsca) wrote :
Changed in charm-kubernetes-master:
assignee: nobody → Cory Johns (johnsca)
status: New → Fix Committed
Changed in cdk-addons:
status: New → Fix Committed
Changed in charm-kubernetes-worker:
status: New → Fix Committed
Changed in cdk-addons:
assignee: nobody → Cory Johns (johnsca)
importance: Undecided → Wishlist
Changed in charm-kubernetes-master:
importance: Undecided → Wishlist
Changed in charm-kubernetes-worker:
importance: Undecided → Wishlist
assignee: nobody → Cory Johns (johnsca)
Changed in cdk-addons:
milestone: none → 1.16
Changed in charm-kubernetes-master:
milestone: none → 1.16
Changed in charm-kubernetes-worker:
milestone: none → 1.16
Changed in cdk-addons:
status: Fix Committed → Fix Released
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.