Closed steinwelberg closed 2 months ago
We also noticed that the first time the policy gets deployed, the same error is triggered.
On policy binding creation, if the resource fails to create because a user/group/policy doesn't exist - it should retry until success. In your case, did this happen?
The MinioPolicyBinding CR does not get deleted when we remove the MinioUser, MinioPolicy and MinioPolicyBinding objects from a cluster at the same time.
This shouldn't happen! Taking a look.
I've put in the following code that addresses the issues you were facing re: MinioPolicyBinding resource deletion.
You can try these changes out yourself with either of the following images:
docker.io/benfiola/minio-operator-ext:latest
docker.io/benfiola/minio-operator-ext:1.1.2
We also noticed that the first time the policy gets deployed, the same error is triggered.
On policy binding creation, if the resource fails to create because a user/group/policy doesn't exist - it should retry until success. In your case, did this happen?
The MinioPolicyBinding CR does not get deleted when we remove the MinioUser, MinioPolicy and MinioPolicyBinding objects from a cluster at the same time.
This shouldn't happen! Taking a look.
Yeah, on resource creation, the problem resolves itself! Just wanted to mention it here to be complete.
Great. Will have a look!
Alright, I have verified that it works as expected! Thanks for the quick response and fix! 💪
The MinioPolicyBinding CR does not get deleted when we remove the MinioUser, MinioPolicy and MinioPolicyBinding objects from a cluster at the same time.
Deleting the policy binding fails with the following error (logs from the operator):
For completeness all delete resource logs are included. Btw, both the bucket and the user have the name
ci-e0eb02dd-typescript-react-template
.We also noticed that the first time the policy gets deployed, the same error is triggered.