mirror of
https://github.com/minio/docs.git
synced 2025-04-27 18:36:56 +03:00
23253dd71c
Addresses #1273 # Summary This pass does three things: 1. Updates all tutorials related to Operator/Tenant deployment for Kustomize and Helm 2. Removes references to Operator Console + updates to reference Kustomize/Helm wherever possible 3. Slightly tidies up old or dangling references This pass does not do these things: - Link out heavily to Kubernetes docs (for later) - Clean up organization (singleplat build handles this) - Addresses OpenShift, Rancher, etc. --------- Co-authored-by: Andrea Longo <feorlen@users.noreply.github.com> Co-authored-by: Allan Roger Reid <allanrogerreid@gmail.com> Co-authored-by: Daryl White <53910321+djwfyi@users.noreply.github.com>
73 lines
2.4 KiB
ReStructuredText
73 lines
2.4 KiB
ReStructuredText
.. _minio-k8s-delete-minio-tenant:
|
|
|
|
=====================
|
|
Delete a MinIO Tenant
|
|
=====================
|
|
|
|
.. default-domain:: minio
|
|
|
|
.. contents:: Table of Contents
|
|
:local:
|
|
:depth: 1
|
|
|
|
Prerequisites
|
|
-------------
|
|
|
|
MinIO Kubernetes Operator
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
This procedures on this page *requires* a valid installation of the MinIO Kubernetes Operator and assumes the local host has a matching installation of the MinIO Kubernetes Operator.
|
|
This procedure assumes the latest stable Operator, version |operator-version-stable|.
|
|
|
|
See :ref:`deploy-operator-kubernetes` for complete documentation on deploying the MinIO Operator.
|
|
|
|
|
|
Tenant Persistent Volume Claims
|
|
-------------------------------
|
|
|
|
The delete behavior of each Persistent Volume Claims (``PVC``) generated by the Tenant depends on the :kube-docs:`Reclaim Policy <concepts/storage/persistent-volumes/#reclaim-policy>` of its bound Persistent Volume (``PV``):
|
|
|
|
- For ``recycle`` or ``delete`` policies, the command deletes the ``PVC``.
|
|
|
|
- For ``retain``, the command retains the ``PVC``.
|
|
|
|
.. warning::
|
|
|
|
Deletion of the underlying ``PV``, whether automatic or manual, results in the loss of any objects stored on the MinIO Tenant.
|
|
|
|
Perform all due diligence in ensuring the safety of stored data *prior* to deleting the Tenant.
|
|
|
|
Procedure
|
|
---------
|
|
|
|
.. tab-set::
|
|
|
|
.. tab-item:: Kustomization
|
|
|
|
You can delete a Kustomization-installed Tenant by deleting the namespace:
|
|
|
|
.. code-block:: shell
|
|
|
|
kubectl delete namespace TENANT-NAMESPACE
|
|
|
|
Replace ``TENANT-NAMESPACE`` with the name of the namespace to remove.
|
|
|
|
.. important::
|
|
|
|
Ensure you have specified the correct namespace for removal before running the command.
|
|
Namespace removal occurs at the Kubernetes layer, such that the MinIO Operator cannot interfere with nor undo the operation.
|
|
|
|
.. tab-item:: Helm
|
|
|
|
You can delete a Helm-installed namespace by using the ``helm uninstall`` command:
|
|
|
|
.. code-block:: shell
|
|
|
|
helm uninstall --namespace MINIO-TENANT TENANT-NAME minio-operator/tenant
|
|
|
|
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.
|