glasskube/operator

[BUG]: Minio Bucket can not be created if name would be longer than 63 characters

kosmoz opened this issue · 0 comments

kosmoz commented

Checklist

  • I've searched for similar issues and couldn't find anything matching
  • I've included steps to reproduce the behavior

Glasskube Version

No response

Kubernetes Version

No response

Host OS and its Version

No response

Steps to reproduce

Create a Vault with name "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa" in namespace "default".

Expected behaviour

The Minio bucket is created and Database Backups and WAL are streamed to the bucket.

Actual behaviour

The bucket can not be created to to the name not being compliant with the S3 bucket naming rules. As a result the database volume fills up very quickly since the WAL files are never archived.

Additional Information

We should truncate the bucket name if it would be to long. Additionally, we should append a hash to the bucket name if it has to be truncated in order to prevent name collisions.