Increase minio secret key length for FIPS

[showuon]

Type of change

Select the type of your PR

• Enhancement / new feature

Description

We disabled FIPS test for tiered storage system test because of the issue: Aiven-Open/tiered-storage-for-apache-kafka#573 . After investigation, I found it's because the secret key length we set is too short, which is not compatible with FIPS compliance. After increasing the secret key size, the test passes.

Checklist

Please go through this checklist and make sure all applicable tasks have been done

• Write tests
• [V] Make sure all tests pass
• Update documentation
• Check RBAC rights for Kubernetes / OpenShift roles
• Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
• Reference relevant issue(s) and close them after merging
• Update CHANGELOG.md
• Supply screenshots for visual changes, such as Grafana dashboards

[im-konge]

LGTM, I guess that the issue in Aiven Tiered Storage plugin should be closed?

[scholzj]

/azp run build

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[scholzj]

/azp run regression

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[showuon]

I guess that the issue in Aiven Tiered Storage plugin should be closed?

No, I'd like to test FIPS support in real AWS S3. Will leave comment in the Aiven's issue when completed.

[showuon]

I guess that the issue in Aiven Tiered Storage plugin should be closed?

No, I'd like to test FIPS support in real AWS S3. Will leave comment in the Aiven's issue when completed.

OK, I've confirmed the openshift cluster with FIPS enabled can upload log segment to AWS S3, and read from S3 without error. I'll leave a comment in the Aiven's issue. Thanks.

[im-konge]

@showuon thanks a lot for the investigation and fixup! 🙂