Add a New Object Storage Provider

نظره عامه ​

ال objectStorage.providers registry in helm_aio accepts new providers without any chart-template change. Adding a backend that is not (yet) bundled is therefore a values-file edit. This page documents the three things a new provider needs and walks through the procedure for adding one to a running install.

The same procedure works for any S3-compatible backend, including the currently-planned Garageو الأعشاب البحرية FS ahead of their official bundled support.

Three things a new provider needs​

ال ilum-objectstorage Service alias is a label-selector خدمة . For its endpoints to resolve, the new provider must satisfy three requirements:

1. A reachable Service in the release namespace. The provider can either expose its own خدمة (preferred) or piggyback on the alias. The provider's own خدمة makes direct probing easier during testing.
2. Pods carrying two labels. Every pod backing the new provider must carry app.kubernetes.io/name: <provider>و app.kubernetes.io/instance: <release>. The alias Service selector matches both labels.
3. A registry entry under objectStorage.providers.<name>. The entry declares the provider's iframe path and console routing mode for the إيلوم UI.

Step-by-step recipe​

The example below adds الأعشاب البحرية FS to an existing install. The same shape applies to any provider.

Step 1. Deploy the provider's chart in the release namespace​

Install the provider's own Helm chart, or run a hand-rolled نشر plus خدمة . The نشر must label its pods with both app.kubernetes.io/nameو app.kubernetes.io/instance:

apiVersion : التطبيقات / الإصدار 1 
نوع : نشر 
البيانات الوصفية : 
  اسم :  seaweedfs
  Namespace : إيلوم 
  تسميات : 
    app.kubernetes.io/name:  seaweedfs
    app.kubernetes.io/instance: إيلوم 
المواصفات : 
  النسخ المتماثله :  1 
  محدد : 
    matchLabels : 
      app.kubernetes.io/name:  seaweedfs
      app.kubernetes.io/instance: إيلوم 
  قالب : 
    البيانات الوصفية : 
      تسميات : 
        app.kubernetes.io/name:  seaweedfs
        app.kubernetes.io/instance: إيلوم 
    المواصفات : 
      حاويات : 
        -  اسم : ملقم 
          صورة :  chrislusf/seaweedfs: أخير 
          أرجس :  [ "server",  "-s3"] 
          الموانئ : 
            -  { containerPort:  9000 ,  اسم : ق3 - واجهة برمجة التطبيقات } 
            -  { containerPort:  9001,  اسم : ق3 - console} 

The pod IP is what the ilum-objectstorage Service alias will route to once the registry is updated.

Step 2. Register the provider in the chart values​

Add the entry under objectStorage.providers.<name> and set the activeProvider override so the alias targets the new provider:

helm upgrade ilum ilum/helm_aio \
--إعادة استخدام القيم \ 
  --set objectStorage.providers.seaweedfs.enabled=true \
  --set objectStorage.providers.seaweedfs.consolePath=/external/seaweed/ \
  --set objectStorage.providers.seaweedfs.consoleMode=nginx-rewrite \
  --set objectStorage.activeProvider=seaweedfs

Step 3. Verify the alias selector​

The alias annotation should reflect the new active provider, and its endpoints should resolve to the new provider's pod IP:

kubectl -n ilum get svc ilum-objectstorage -o jsonpath='{.metadata.annotations.ilum\.cloud/object-storage-active-provider}{"\n"}'
# Expected: seaweedfs

kubectl -n ilum get endpoints ilum-objectstorage
# Expected ENDPOINTS: <pod-ip>:9001,<pod-ip>:9000

Step 4. Verify the UI iframe path​

ال ILUM-UI ConfigMap should expose the new console path:

kubectl -n ilum get configmap ilum-ui -o jsonpath='{.data.ILUM_OBJECT_STORAGE_PATH}{"\n"}'
# Expected: /external/seaweed/

Hard-reload the إيلوم UI in the browser. The Object Storage nav button should load the new provider's console inside the iframe.

consoleMode: same-origin vs nginx-rewrite​

The registry's consoleMode field controls how the إيلوم UI's nginx reverse proxy renders /external/object-storage/ and the provider-specific path.

When unsure, start with nginx-rewrite. It is the safer default for consoles that have not been built with إيلوم -aware base-path awareness.

What still needs hand-wiring​

The registry handles alias selection, the UI iframe path, and the /external/object-storage/ redirect. The following items remain the operator's responsibility for a non-bundled provider:

• Bucket bootstrap. Run the equivalent of the bundled init-rustfs-bucketsأو init-minio-policies مهمة against the new provider. The bucket list is documented under objectStorage.defaultBuckets.
• Credentials. Either share the ilum-objectstorage-credentials Secret (the simplest option) or override the provider's chart values to read from a provider-specific Secret.
• OIDC integration. The bundled Hydra integration plugs into ميني آيو through MINIO_IDENTITY_OPENID_* env vars. New providers must supply their own OIDC adapter.
• Bucket policies. The bundled chart applies two policies (readilum, readwriteilum) to ميني آيو و RustFS on first install. Other providers need an equivalent.
• Console UX testing.ال إيلوم UI iframe wraps the provider's own console. Cross-origin asset URLs, auto-redirects, and form submissions vary across providers. Test the embedded experience before flipping the active provider in production.

Reference​

• Provider page template: copy /user-guides/object-storage/providers/_template.md for documentation.
• Helm values: Object Storage Helm Values
• Existing provider pages: ميني آيو · RustFS · External S3 · Garage (planned) · SeaweedFS (planned)
• Troubleshooting: Troubleshoot Object Storage