Closed pomland-94 closed 5 months ago
Hi @pomland-94 ,
I could see this error related to bucket name from provisioning pod using your values:
$ kubectl logs minio-cluster-provisioning-7z4rv
Warning: Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
Defaulted container "minio" out of: minio, wait-for-available-minio (init)
Start Minio provisioning
Added `provisioning` successfully.
Successfully applied new settings.
Please restart your server 'mc admin service restart provisioning'.
Restart command successfully sent to `provisioning`. Type Ctrl-C to quit or wait to follow the status of the restart process.
┌────────────────────────────────────────────────────┬────────┐
│ HOST │ STATUS │
├────────────────────────────────────────────────────┼────────┤
│ minio-1.minio-headless.test.svc.cluster.local:9000 │ ✔ │
│ minio-0.minio-headless.test.svc.cluster.local:9000 │ ✔ │
│ minio-2.minio-headless.test.svc.cluster.local:9000 │ ✔ │
│ minio-3.minio-headless.test.svc.cluster.local:9000 │ ✔ │
└────────────────────────────────────────────────────┴────────┘
Restarted `provisioning` successfully in 1 seconds
Bucket created successfully `provisioning/artifacts`.
Successfully set bucket quota of 20 GiB on `artifacts`
provisioning/artifacts versioning is enabled
mc: <ERROR> Unable to make bucket `provisioning/external_diffs`. Bucket name contains invalid characters
I hope it helps
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.
Name and Version
bitnami/minio:14.1.7
What architecture are you using?
arm64
What steps will reproduce the bug?
Hey, I tried to Deploy a Minio Cluster in distributed mode inside my Kubernetes Cluster, but the Deployment does not working. I get several Errors inside the minio pods:
Are you using any custom parameters or values?
What is the expected behavior?
No response
What do you see instead?
The provisioning Job does not Succeed and the minio cluster does not come up.
Job:
Pod logs:
Additional information
No response