I have minio running in the same cluster as Speckle. Both are installed from official Helm charts.
Speckle works and is talking to a database and everything provided file uploads are turned off. Minio is up and I can talk to it from my laptop, create buckets, upload files etc. via portforwarding. Minio is running on port 9000 without tls.
However, if I enable file uploads, the speckle-server and speckle-objects pods no longer start. They just get to Init BlobStorage module and hang, with k8s restarting them every ten minutes or so. No errors.
The result is the same whether or not I specify a port in the endpoint, whether or not the port is set in the s3.networkPolicy section of my values and whether I set the protocol to http or https. BUT there does appear to be some sort of connection, at least if I change the endpoint to something that doesn’t exist, I get a relevant error and a container crash.
I’m wondering if this is due to some sort of network policy that’s needed? I’m not too well-versed in that part of Kubernetes, but I have filled out the sections in the values.yaml:
podSelector: { matchLabels: { "statefulset.kubernetes.io/pod-name": "minio-speckle-dev-pool-0-0" } }
namespaceSelector: { matchLabels: { "kubernetes.io/metadata.name": "minio-tenant" } }
Any pointers would be appreciated.