Deploy a Silo Tenant

This procedure deploys a Silo server image as a Tenant managed by MinIO Operator v7.1.1. The upstream Operator repository was archived and made read-only on 2026-03-20, so this is a frozen compatibility baseline rather than an actively maintained Operator path. MinIO Operator, Tenant, the minio.min.io API group, and the CRD field names are upstream Kubernetes contracts and therefore retain their original names.

The verified baseline below creates a four-server Tenant. A single-node topology is useful for local testing, but its production failure model and storage layout are outside the scope of this procedure.

This documentation assumes familiarity with all referenced Kubernetes concepts, utilities, and procedures. While this documentation may provide guidance for configuring or deploying Kubernetes-related resources on a best-effort basis, it is not a replacement for the official Kubernetes Documentation.

Deploy a Silo Tenant using Kustomize

The following procedure uses the base Kustomization template from the MinIO Operator v7.1.1 repository, then replaces its upstream MinIO image default with a pinned Silo image.

You can select a different v7.1.1 example as your starting point, or build your own resources using the MinIO Custom Resource Documentation. No later supported upstream release exists; review any fork, replacement, or CRD change independently before departing from this pinned snapshot.

This procedure is not exhaustive of all possible configuration options available in the Tenant CRD. It provides a baseline from which you can modify and tailor the Tenant to your requirements.

1. Create a YAML object for the Tenant

   Clone the pinned Operator release and use kubectl kustomize to produce a YAML file containing all Kubernetes resources necessary to deploy the base Tenant:

   BASH

   git clone --branch v7.1.1 --depth 1 https://github.com/minio/operator.git
   kubectl kustomize operator/examples/kustomization/base > tenant-base.yaml

   The command creates a single YAML file with multiple objects separated by the --- line. Open the file in your preferred editor.

   The upstream template defaults to quay.io/minio/minio. Before applying it, set the kind: Tenant object’s spec.image to the verified Silo release and disable the inherited in-place updater:

   YAML

   spec:
     image: pgsty/minio:RELEASE.2026-08-04T00-00-00Z
     env:
       - name: MINIO_UPDATE
         value: "off"

   Pin the image by tag or digest. If you choose a newer Silo image, review and test that release explicitly instead of inheriting the Operator template’s upstream image.

   The following steps reference each object based on its kind and metadata.name fields:

2. Configure the Tenant topology

   The kind: Tenant object describes the Silo workload managed by MinIO Operator.

   The following fields share the spec.pools[0] prefix and control the number of servers, volumes per server, and storage class of all pods deployed in the Tenant:

   Field	Description
   servers	The number of Silo pods to deploy in the Server Pool.
   volumesPerServer	The number of persistent volumes to attach to each Silo pod (servers). The Operator generates volumesPerServer x servers Persistent Volume Claims for the Tenant.
   volumeClaimTemplate.spec.storageClassName	The Kubernetes storage class to associate with the generated Persistent Volume Claims. If no storage class exists matching the specified value or if the specified storage class cannot meet the requested number of PVCs or storage capacity, the Tenant may fail to start.
   volumeClaimTemplate.spec.resources.requests.storage	The amount of storage to request for each generated PVC.

3. Configure Tenant Affinity or Anti-Affinity

   The MinIO Operator supports the following Kubernetes Affinity and Anti-Affinity configurations:

   • Node Affinity (spec.pools[n].nodeAffinity)
   • Pod Affinity (spec.pools[n].podAffinity)
   • Pod Anti-Affinity (spec.pools[n].podAntiAffinity)

   For production, configure Pod Anti-Affinity so that the Kubernetes scheduler does not place multiple Tenant pods on the same worker node.

   If you have specific worker nodes on which you want to deploy the tenant, pass those node labels or filters to the nodeAffinity field to constrain the scheduler to place pods on those nodes.

4. Configure Network Encryption

   The MinIO Tenant CRD provides the following fields for configuring Tenant TLS network encryption:

   Field	Description
   spec.requestAutoCert	Enable or disable Silo automatic TLS certificate generation. Defaults to true if omitted.
   spec.certConfig	Customize the behavior of automatic TLS, if enabled.
   spec.externalCertSecret	Enable TLS for multiple hostnames via Server Name Indication (SNI) Specify one or more Kubernetes secrets of type kubernetes.io/tls or cert-manager.
   spec.externalCaCertSecret	Enable validation of client TLS certificates signed by unknown, third-party, or internal Certificate Authorities (CA). Specify one or more Kubernetes secrets of type kubernetes.io/tls containing the full chain of CA certificates for a given authority.

5. Configure Silo Environment Variables

   Silo preserves the upstream MINIO_* environment-variable contract. You can supply these variables using the Secret referenced by the Tenant CRD’s spec.configuration field, or use spec.env for individual values such as MINIO_UPDATE.

   Field	Description
   spec.configuration.name	Specify a Kubernetes opaque Secret whose config.env key contains the upstream-compatible environment variables to set. Use plain text under stringData.config.env, as in the v7.1.1 base template. If you use data.config.env instead, its value must be base64-encoded.

   The YAML includes an object kind: Secret with metadata.name: storage-configuration that sets the root username, password, erasure parity settings, and enables Tenant Console.

   Modify this as needed to reflect your Tenant requirements.

6. Review the Namespace

   The YAML object kind: Namespace sets the default namespace for the Tenant to minio-tenant.

   You can change this value to create a different namespace for the Tenant. You must change all metadata.namespace values in the YAML file to match the Namespace.

7. Deploy the Tenant

   Use the kubectl apply -f command to deploy the Tenant.

   BASH

   kubectl apply -f tenant-base.yaml

   The command creates each of the resources specified in the YAML object at the configured namespace.

   You can monitor the progress using the following command:

   BASH

   watch kubectl get all -n minio-tenant

8. Expose the Tenant S3 API port

   To test the Silo client mc from your local machine, forward the S3 API port and create an alias.

   • Forward the Tenant’s S3 API port:
   BASH

   kubectl port-forward svc/MINIO_TENANT_NAME-hl 9000 -n MINIO_TENANT_NAMESPACE

   • Create an alias for the Tenant service:
   BASH

   mc alias set myminio https://localhost:9000 minio minio123 --insecure

   You can use mc mb to create a bucket on the Tenant:

   BASH

   mc mb myminio/mybucket --insecure

   If you deployed the Tenant using TLS certificates minted by a trusted Certificate Authority (CA), you can omit the --insecure flag.

   See Connect to the Tenant for specific instructions.

Connect to the Tenant

MinIO Operator creates Kubernetes Services for the Silo Tenant. Their generated names remain part of the Operator contract.

Use the kubectl get svc -n NAMESPACE command to review the deployed services. For Kubernetes services which use a custom kubectl analog, you can substitute the name of that program.

kubectl get svc -n minio-tenant-1

NAME                               TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE
minio                              LoadBalancer   10.97.114.60     <pending>     443:30979/TCP    2d3h
TENANT-NAMESPACE-console           LoadBalancer   10.106.103.247   <pending>     9443:32095/TCP   2d3h
TENANT-NAMESPACE-hl                ClusterIP      None             <none>        9000/TCP         2d3h

• The minio service exposes the Tenant S3 API. Applications should use this service for S3 operations against Silo.
• The *-console service exposes the Silo Console. Administrators can use this service for browser-based management.

The remaining services support Tenant operations and are not intended for consumption by users or administrators.

By default each service is visible only within the Kubernetes cluster. Applications deployed inside the cluster can access the services using the CLUSTER-IP.

Applications external to the Kubernetes cluster can access the services using the EXTERNAL-IP. This value is only populated for Kubernetes clusters configured for Ingress or a similar network access service. Kubernetes provides multiple options for configuring external access to services.

See the Kubernetes documentation on Publishing Services (ServiceTypes) and Ingress for more complete information on configuring external access to services.

For specific flavors of Kubernetes, such as OpenShift or Rancher, defer to the service documentation on the preferred or available methods of exposing Services to internal or external access.