The Helm chart currently creates buckets and will always change the versioning to either versioned or suspended (after which the bucket can no longer be reverted to unversioned).

Expected Behavior

The created buckets should be able to stay unversioned, as versioning suspeded can trigger unwanted behaviour.

Current Behavior

If you list an array of buckets to be created as such:

  buckets:
    - name: backups
      expiryDays: 90

The post job will create the bucket as unversioned, but then immediately change it to versioning suspended in this if case: https://github.com/minio/minio/blob/0a36d41dcd86fa7cfe8a2077e9f6f7bbb6a88d02/helm/minio/templates/_helper_create_bucket.txt#L89C1-L91C1

Possible Solution

If the default would be change from false to null I think this would solve it.

Context

This causes our tempo storage to grow since when tempo deleted old traces, the data is still there.