When delete bucketAccess, the driver name is not verified in the delete operation of bucketAccess Controller #80
Description
Bug Report
What happened:
Deploying COSI sidecar component pod of two different storage vendors. When delete bucketAccess，an unrelated storage vendor component also received a deletion request for this bucketAccess.
What you expected to happen:
Drivers must be differentiated regardless of whether they are created or deleted operation.
When delete bucketAccess, an unrelated storage vendor component will not received a deletion request for this bucketAccess.
How to reproduce this bug (as minimally and precisely as possible):
1、Deploying COSI sidecar component pod of two different storage vendors.
2、create a bucketClaim and a related bucketAccess.
3、delete this bucketAccess.
Anything else relevant for this bug report?:
1、the driver name is not verified in the delete operation of Controller.
2、related code: pkg/bucketaccess/bucketaccess_controller.go.
Environment:
- Kubernetes version (use
kubectl version), please list client and server: - Sidecar version (provide the release tag or commit hash):
- Provisoner name and version (provide the release tag or commit hash):
- Cloud provider or hardware configuration:
- OS (e.g:
cat /etc/os-release): - Kernel (e.g.
uname -a): - Install tools:
- Network plugin and version (if this is a network-related bug):
- Others: