S3Instance is not reconcilied if some S3User/Buckets/Policies depends on a wrong/unhealthy S3Instance

[aslafy-z]

I've deployed s3-operator 0.12.0 with

• S3Instance
• S3User
• Bucket
• Policy

I made some mistake in the S3Instance configuration and was missing RBAC for s3-operator to be able to read the minio tenant secret.

The whole setup was blocked because S3Instance was reporting a unhealthy status.

I had to force delete (remove finalizers) all descendent resources (S3User, Bucket, Policy) and rollout the operator for it to take updates on the S3Instance resources.

These objects should be reconciled in a async way, descendent resources should not block reconciliation of a upstream resource.

[graindcafe]

In addition : when creating a resource that cannot be reconcilled (access denied, instance unreachable, …), the resource cannot be deleted without manually deleting its finalizer. When requesting the deletion of the resourcen, the S3 Operator try to delete it from the S3 Instance even if the resource has never been created there. So it fails to delete it from the S3 Instance and the finalizer fails, preventing the deletion from k8s.