Error on self signed Minio

[DevFontes]

I'm using csi-s3 on a kubernetes 1.28 cluster and an internal self signed Minio. I'm having a problem provisioning a PV, this is the pod log:

I1206 12:58:59.897114 1 controller.go:1335] provision "default/pvc-test" class "csi-s3": started
I1206 12:58:59.897341 1 event.go:282] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"pvc-test", UID:"94a96d3f-14fd-4261-9681- c87e2578803d", APIVersion:"v1", ResourceVersion:"4756158", FieldPath:""}): type: 'Normal' reason: 'Provisioning' External provisioner is provisioning volume for claim "default/pvc-test"
I1206 12:59:09.900053 1 controller.go:1109] Temporary error received, adding PVC 94a96d3f-14fd-4261-9681-c87e2578803d to claims in progress
W1206 12:59:09.900089 1 controller.go:961] Retrying syncing claim "94a96d3f-14fd-4261-9681-c87e2578803d", failure 0
E1206 12:59:09.900121 1 controller.go:984] error syncing claim "94a96d3f-14fd-4261-9681-c87e2578803d": failed provision to provision volume with StorageClass "csi-s3": rpc error: code = DeadlineExceeded desc = context deadline exceeded

[afgane]

I don't have a suggestion as to why this might be happening (perhaps @nuwang can chime in). However, I can say that the for us performance when using csi-s3 was not good so we reverted back to cvmfs-csi. Also, Galaxy 23.1 (currently latest) will not run on K8s >1.25 (until this is merged galaxyproject/galaxy#15238) and I wonder if there could be an issue here with csi-s3 as well with 1.28...

[almahmoud]

@DevFontes Is this in the context of using Galaxy Helm chart? If not, perhaps it might be more useful to open an issue at the csi-s3 repository (https://github.com/ctrox/csi-s3/issues) as the packaged chart is in this repository, but csi-s3 itself is not maintained by this team