Skip to content

Breaking Changes

2.0.33

Bundled object storage: MinIO image replaced by Silo

MinIO no longer publishes community container images. The default minio.image is now Silo (docker.io/pgsty/silo), a community-maintained fork of MinIO.

Who is affected: deployments with minio.enabled: true. Deployments using an external S3 service are not affected.

What changes: only the server image of the MinIO Tenant. Silo keeps the MinIO storage format and MINIO_* configuration, so the existing tenant volumes are reused as-is. The MinIO Operator (quay.io/minio/operator, quay.io/minio/operator-sidecar) is still required.

Before upgrading: - Back up your bucket (for example with mc mirror). - Air-gapped / restricted registries: mirror docker.io/pgsty/silo:RELEASE.2026-09-16T00-00-00Z and allow docker.io/pgsty/silo. - If you override minio.image, update it to a Silo release.

Upgrade: the S3 endpoint is unavailable while the operator rolls the tenant pods, and in-flight writes may fail. Scale down OpenAEV (platform, injectors, collectors, XTM Composer) before helm upgrade, wait for the tenant to be healthy, then scale back up.

Before

minio:
  image:
    repository: quay.io/minio/minio
    tag: RELEASE.2025-06-13T11-33-47Z

After

minio:
  image:
    repository: docker.io/pgsty/silo
    tag: RELEASE.2026-09-16T00-00-00Z