Skip to content

Check other source for provisioner name #49

@disrani-px

Description

@disrani-px

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):

  1. Create PVC
  2. Delete StorageClass
  3. Start pod which uses PVC.
  4. 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:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions