Service: Silo - EyevinnOSC/community GitHub Wiki
Silo (serviceId pgsty-silo) is an independent, community-maintained fork of the open source MinIO server, published by PGSTY (Pigsty). It provides S3-compatible object storage with a web console and preserves S3 API and storage-format compatibility, including the MINIO_* environment variables. Silo is not affiliated with or endorsed by MinIO, Inc. In Eyevinn Open Source Cloud (OSC) it is a long-running service instance with a 50 GiB persistent volume, running release RELEASE.2026-09-16T00-00-00Z. License: AGPL-3.0. For the original upstream build, see the MinIO service.
- Provide an S3-compatible endpoint for backups, artifacts, media assets or application data.
- Serve a web console at
<instance-url>/ui/. - Work with any S3-compatible client or SDK using the root user as access key.
Silo has no dependencies on other OSC services. Store the root password as a service secret first with create-service-secret (serviceId: "pgsty-silo", for example name silorootpassword, value a long random string). Then create the instance with create-service-instance using serviceId: "pgsty-silo". The instance name must be alphanumeric and at most 20 characters.
{
"name": "mystorage",
"RootUser": "<access-key>",
"RootPassword": "{{secrets.silorootpassword}}"
}Wait with wait-for-service-ready or get-instance-status, then read the URL with describe-service-instance. The URL has the form https://<tenant>-<name>.pgsty-silo.auto.prod-se.osaas.io and is both the S3 endpoint and the base of the web console (<URL>/ui/). The health endpoint <URL>/minio/health/live returns 200 when the server is up. Right after the instance first reports ready, S3 requests can return 401 for a short while; wait and retry.
| Option | Required | Type | Meaning |
|---|---|---|---|
| name | Yes | string | Name of the instance. Letters, digits and underscore only; on OSC at most 20 characters (lowercase letters and digits recommended). |
| RootUser | Yes | string | Name of the root (admin) user. Used as the S3 access key. Feeds MINIO_ROOT_USER. |
| RootPassword | Yes | string, sensitive | Password of the root user. Used as the S3 secret key. Use a long random value; store as a service secret and pass as {{secrets.NAME}}. Feeds MINIO_ROOT_PASSWORD. |
A {{secrets.NAME}} reference must be the whole field value. The root credentials are set when the instance is created.
Configure any S3-compatible client with:
| Setting | Value |
|---|---|
| Endpoint URL | https://<tenant>-<name>.pgsty-silo.auto.prod-se.osaas.io |
| Access key | the RootUser value |
| Secret key | the RootPassword value |
| Region | us-east-1 |
| Addressing style | path-style |
Create a bucket (for example my-bucket), upload a file and download it again to confirm. Requests without valid credentials, or with a wrong password, are rejected with HTTP 403.
- Single node, single drive: there is no redundancy. Data lives only on the 50 GiB persistent volume, so keep an independent copy of important data.
- Use path-style addressing. Virtual-hosted style (bucket as subdomain) is not available with this hostname pattern.
- Do not rely on IP-based bucket policy conditions (
aws:SourceIp). - Changing RootUser or RootPassword after creation is not verified to work.