You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, cleanup s3 bucket path depending on the S3 credentials used by MO cluster and claim S3 bucket does not require credential in the controller, which incurs several problems:
s3 bucket path would be claimed even if the credential is bad (since we don't need the credential on claiming);
for the same reason, operator might not be abled to cleanup the claimed s3 bucket path since the credential might be bad;
Also, use mo's credentials require the namespace of the cluster exist, but the bucket is actually has decoupled lifecycle with the namespace.
Additional information
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for enhancement?
What would you like to be added ?
enhance s3 bucket lifecycle management strategy.
Why is this needed ?
Currently, cleanup s3 bucket path depending on the S3 credentials used by MO cluster and claim S3 bucket does not require credential in the controller, which incurs several problems:
Also, use mo's credentials require the namespace of the cluster exist, but the bucket is actually has decoupled lifecycle with the namespace.
Additional information
No response
The text was updated successfully, but these errors were encountered: