zeekay
679a9bed4f
- Replace all MinIO brand references with S3 in docs, helm charts, and comments - Replace quay.io/minio images with ghcr.io/hanzoai/s3 and ghcr.io/hanzos3/* - Replace min.io domains: docs→docs.hanzo.ai, dl→dl.hanzo.space, play→play.hanzo.space - Replace slack.min.io with hanzo.ai/discord - Replace subnet.min.io with subnet.hanzo.ai - Update Makefile REPO to ghcr.io/hanzoai - Update helm values: mc image, OIDC clientId, service account name - Update Go source user-facing URLs and messages - Fix test configs and grafana dashboard descriptions
Deploy S3 on Kubernetes 
S3 is a high performance distributed object storage server, designed for large-scale private cloud infrastructure. S3 is designed in a cloud-native manner to scale sustainably in multi-tenant environments. Orchestration platforms like Kubernetes provide perfect cloud-native environment to deploy and scale S3.
S3 Deployment on Kubernetes
There are multiple options to deploy S3 on Kubernetes:
-
S3-Operator: Operator offers seamless way to create and update highly available distributed S3 clusters. Refer S3 Operator documentation for more details.
-
Helm Chart: S3 Helm Chart offers customizable and easy S3 deployment with a single command. Refer S3 Helm Chart documentation for more details.
Monitoring S3 in Kubernetes
S3 server exposes un-authenticated liveness endpoints so Kubernetes can natively identify unhealthy S3 containers. S3 also exposes Prometheus compatible data on a different endpoint to enable Prometheus users to natively monitor their S3 deployments.