The consecutive delete and create operations of bucketAccess is not processed correctly by BucketAccess Controller #151
Description
Bug Report
What happened:
When a bucketAccess exists in the cluster, we delete this bucketAccess and create a bucketAccess with the same name immediately. However, BucketAccess Controller fails to process the creation operation about this bucketAccess. It seems that the creation of this bucketAccess is not "watched" by BucketAccess Controller.
What you expected to happen:
Consecutive delete and create operations of bucketAccess can be performed by BucketAccess Controller in the correct sequence.
How to reproduce this bug (as minimally and precisely as possible):
1、create a bucketClaim.
2、create a bucketAccess by using this bucketClaim.
3、delete this bucketAccess and create this bucketAccess again.
4、the create operation of this bucketAccess is not "watched" by BucketAccess Controller.
Anything else relevant for this bug report?:
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: