I'm experimenting with kubernetes and a minio deployment. I have a k3s 4 node cluster, each one with 4 50GB disk. Following the instructions here I have done this:
First I installed krew in order to install the minio and the directpv operators.
I installed those two without a problem.
I formatted every Available hdd in the node using
kubectl directpv drives format --drives /dev/vd{b...e} --nodes k3s{1...4}I then proceed to make the deployment, first I create the namespace with
kubectl create namespace minio-tenant-1, and then I actually create the tenant with:kubectl minio tenant create minio-tenant-1 --servers 4 --volumes 8 --capacity 10Gi --storage-class direct-csi-min-io --namespace minio-tenant-1The only thing I need to do then is expose the port to access, which I do with:
kubectl port-forward service/minio 443:443(I'm guessing it should be a better way to achieve this, as the last command isn't apparently permanent, maybe using a LoadBalancer or NodePort type services in the kubernetes cluster).
So far so good, but I'm facing some problems:
- When I try to create an alias to the server using mc the prompt answer me back with:
mc: Unable to initialize new alias from the provided credentials. Get "https://127.0.0.1/probe-bucket-sign-9aplsepjlq65/?location=": x509: cannot validate certificate for 127.0.0.1 because it doesn't contain any IP SANs
I can surpass this with simply adding the --insecure option, but I don't know why it throws me this error, I guess is something how k3s manage the TLS auto-signed certificates.
Once created the alias (I named it test) of the server with the
--insecureoption I try to create a bucket, but the server always answer me back with:mc mb test/hellomc: <ERROR> Unable to make bucket \test/hello. The specified bucket does not exist.
So... I can't really use it... Any help will be appreciated, I need to know what I'm doing wrong.