-
Notifications
You must be signed in to change notification settings - Fork 89
Check other source for provisioner name #49
Copy link
Copy link
Closed
Milestone
Description
Is this a BUG REPORT or FEATURE REQUEST?:
BUG REPORT
What happened:
The Portworx driver checks the storage class to determine if a volume has been provisoned by it.
The storage class can be deleted after a PVC has been provisioned though. So we need to use other methods to check the provisioner
What you expected to happen:
Should be able to detect that a PVC was provisioned by Portworx even after the storageclass has been deleted.
How to reproduce it (as minimally and precisely as possible):
- Create PVC
- Delete StorageClass
- Start pod which uses PVC.
- Stork logs should complain about not being able to find storage class
Anything else we need to know?:
Environment:
- Kubernetes version (use
kubectl version): - Cloud provider or hardware configuration:
- OS (e.g. from /etc/os-release):
- Kernel (e.g.
uname -a): - Install tools:
- Others:
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels