मुख्य विषयवस्तु में जाएं

मिनियो

विहंगावलोकन​

मिनियो is the default object storage backend for इलम in the 6.7.x line. The Bitnami मिनियो chart is bundled as a sub-chart of helm_aio and renders when minio.enabled है सच्चा, which is the chart default. RustFS is bundled alongside it as an opt-in provider and is planned to become the default in 6.8.0.

Propertyमूल्य
लाइसेंसAGPL-3.0 (server), Apache-2.0 (client mc)
Status in IlumDefault in 6.7.x (opt-in from 6.8.0)
Bundled chartBitnami minio-15.0.7 (mirrored via bitnamilegacy/minio)
Default in helm_aioEnabled (minio.enabled=true)
Distributed modeSupported, follow the Bitnami chart documentation
Console UXFull administrative web console at /बाहरी/मिनी/
OIDC integrationSupported via MINIO_IDENTITY_OPENID_* env vars (Hydra preconfigured)

When to use MinIO​

  • An existing इलम install was provisioned before RustFS shipped and the operator prefers to keep the proven storage layer unchanged.
  • The deployment depends on मिनियो-specific features such as bucket replication, lifecycle policies, IAM policy variables, or KMS integration that the current RustFS alpha does not yet match.
  • A clustered, erasure-coded, multi-node distributed configuration is required today.

Enable MinIO as the active provider​

In the 6.7.x line मिनियो is the default provider, so a net-new install runs on मिनियो with no flags:

helm install ilum ilum/helm_aio

To pin मिनियो explicitly (recommended for 6.8.0 and later, where RustFS becomes the default), set the two Helm flags below. The provider registry under objectStorage.providers.minio ships with sensible defaults; the operator does not need to touch it for a standard install.

helm upgrade ilum ilum/helm_aio \
  --अस्त हो rustfs.enabled=गलत \
  --अस्त हो minio.enabled=सच्चा

वही ilum-objectstorage Service alias selects pods with label app.kubernetes.io/name: minio and routes both consumer S3 traffic and the इलम UI's Object Storage iframe to मिनियो.

Registry entry​

The chart ships the following registry defaults for मिनियो:

objectStorage:
  providers:
    मीनो:
      consolePath: /बाहरी/मिनी/
      consoleMode: nginx-rewrite

वही consoleMode: nginx-rewrite instructs the इलम UI's nginx reverse proxy to redirect requests for /external/object-storage/ तक /बाहरी/मिनी/. मिनियो pins its own console to that absolute URL through the MINIO_BROWSER_REDIRECT_URL environment variable, so the proxy cannot rewrite the path on the fly.

Prometheus metrics​

मिनियो exposes Prometheus-format metrics under /minio/metrics/v3, with category-specific paths appended (for example, /minio/metrics/v3/api और /minio/metrics/v3/cluster). Bearer-token authentication is required by default. Generate a long-lived scrape token with the bundled mc client:

कुबेक्टल -n इलम exec deploy/ilum-core -- \
  mc admin prometheus generate ilum-objectstorage cluster

The command prints a sample Prometheus scrape_config block including the bearer token. Splice the authorization.credentials value into the Prometheus server's configuration.

Operators that prefer an unauthenticated endpoint can set MINIO_PROMETHEUS_AUTH_TYPE=public on the मिनियो deployment to disable the bearer-token requirement. This change is irreversible without a Pod restart.

For the full metrics catalog, refer to MinIO Prometheus metrics.

Known limitations​

  • Single-path console binding. वही मिनियो console is reachable only at /बाहरी/मिनी/. Operators serving इलम behind a non-default base path must update both the MINIO_BROWSER_REDIRECT_URL value and the objectStorage.providers.minio.consolePath entry.
  • Root credentials sealed at first install. मिनियो records the root user when its Pod starts for the first time. Rotating the shared ilum-objectstorage-credentials Secret afterwards does not change the live मिनियो root user. To rotate मिनियो credentials, follow the rotation procedure in Rotate Object Storage Credentials.
  • License. वही मिनियो server is licensed under AGPL-3.0. Operators redistributing इलम के साथ मिनियो enabled should review the obligations that the AGPL imposes on hosted services.

Disable MinIO​

To stop running मिनियो after a migration to another provider, set minio.enabled=false. The chart's pre-upgrade hook detects the existing मिनियो PersistentVolumeClaim and refuses to proceed if disabling मिनियो would orphan it without an acknowledged cutover. Follow the documented migration procedure in Migrate Between Providers to disable मिनियो safely.

Reference​

Last updated on