vSphere Integrator Charm is not using the CSI Plugin for vSphere, but still uses deprecated storage mechanism
Bug #1867947 reported by
Calvin Hartwell
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
CDK Addons |
Fix Released
|
Wishlist
|
Unassigned | ||
Kubernetes Control Plane Charm |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Hi all,
The current storage mechanism used by the vSphere integrator charm is outdated/deprecated and the CSI plugin should be used instead: https:/
Cheers,
- Calvin
no longer affects: | charm-vsphere-integrator |
Changed in cdk-addons: | |
importance: | Undecided → Low |
Changed in charm-kubernetes-master: | |
importance: | Undecided → Low |
Changed in cdk-addons: | |
status: | New → Triaged |
Changed in charm-kubernetes-master: | |
status: | New → Triaged |
Changed in cdk-addons: | |
importance: | Low → Wishlist |
Changed in charm-kubernetes-master: | |
importance: | Low → Wishlist |
tags: | added: sts |
To post a comment you must log in.
Please see the vsphere- cloud-provider[ 1] charm which deploys both the vsphere cloud-controller and vsphere storage provider. This charm follows the upstream sources mentioned in this bug as far as the CSI driver goes as well as deploying the in-cluster cloud controller. This charm can be deployed as a subordinate of the vsphere-integrator charm within the same machine model as kubernetes- control- plane
[1] https:/ /charmhub. io/vsphere- cloud-provider