From f8f0ab934d0d7fab393e6fe859b130847d7bcf17 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Gonzalo=20Pe=C3=B1a-Castellanos?= Date: Thu, 30 Jul 2026 08:36:32 -0500 Subject: [PATCH] docs: note S3-compatible endpoints for storage secrets MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Gonzalo Peña-Castellanos --- docs-gb/kubernetes/storage-secrets.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs-gb/kubernetes/storage-secrets.md b/docs-gb/kubernetes/storage-secrets.md index f63deed034..1b35b2caf4 100644 --- a/docs-gb/kubernetes/storage-secrets.md +++ b/docs-gb/kubernetes/storage-secrets.md @@ -137,6 +137,10 @@ The easiest way to change this is to update your SeldonRuntime. {% tabs %} {% tab title="S3 MinIO" %} +{% hint style="info" %} +The `s3` remote type works with any S3-compatible object store. Amazon S3 requires no `endpoint` parameter, while an S3-compatible provider such as Backblaze B2, Cloudflare R2, or MinIO is selected by setting `provider` and pointing `endpoint` at that provider's published S3 endpoint (for example, `endpoint: https://`). The MinIO example below sets `endpoint` for an in-cluster deployment. +{% endhint %} + Assuming you have installed MinIO in the `minio-system` namespace, a corresponding secret could be: ```yaml