Skip to content

docs(storage-secrets): note S3-compatible endpoints for storage secrets #7116

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
goanpeca wants to merge 1 commit into
base: v2
Choose a base branch
from
Draft

docs(storage-secrets): note S3-compatible endpoints for storage secrets #7116

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs-gb/kubernetes/storage-secrets.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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://<s3-compatible-endpoint>`). 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
Expand Down