InseeFrLab / InseeFrLab/s3-operator

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

Open
#104 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
66
Forks
16
PR merge metrics
No merged PRs in 30d

Description

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.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.