Closes #1291 Missed a few log lines referencing Operator Console. Also cleaning up some broken refs and further simplifying references to the Console when in context of Tenant/MinIO Object Store. --------- Co-authored-by: Andrea Longo <feorlen@users.noreply.github.com>
1.7 KiB
Modify a MinIO Tenant
minio
Table of Contents
You can modify tenants after deployment to change mutable
configuration settings. See minio-operator-crd
for a complete description of
available settings in the MinIO Custom Resource Definition.
The method for modifying the Tenant depends on how you deployed the tenant:
Kustomize
For Kustomize-deployed Tenants, you can modify the base Kustomization
resources and apply them using kubectl apply -k
against the
directory containing the kustomization.yaml
object.
kubectl apply -k ~/kustomization/TENANT-NAME/
Modify the path to the Kustomization directory to match your local configuration.
Helm
For Helm-deployed Tenants, you can modify the base
values.yaml
and upgrade the Tenant using the chart:
helm upgrade TENANT-NAME minio-operator/tenant -f values.yaml -n TENANT-NAMESPACE
The command above assumes use of the MinIO Operator Chart repository. If you installed the Chart manually or by using a different repository name, specify that chart or name in the command.
Replace TENANT-NAME
and TENANT-NAMESPACE
with the name and namespace of the Tenant, respectively. You can use
helm list -n TENANT-NAMESPACE
to validate the Tenant
name.
See minio-tenant-chart-values
for more complete
documentation on the available Chart fields.