mirror of
https://github.com/minio/docs.git
synced 2025-11-04 16:12:00 +03:00
571f188a4e
##
We are going to make the following changes to the Object Store docs as
part of a larger QC/Content pass:
### Left Navigation
We want to modify the left navigation flow to be a natural progression
from a basic setup to more advanced.
For example:
- Core Concepts
- Deployment Architecture
- Availability and Resiliency
- Erasure Coding and Object Healing
- Object Scanner
- Site Replication and Failover
- Thresholds and Limits
- Installation
- Deployment Checklist
- Deploy MinIO on Kubernetes
- Deploy MinIO on Red Hat Linux
- Deploy MinIO on Ubuntu Linux
- Deploy MinIO for Development (MacOS, Windows, Container)
- Security and Encryption (Conceptual Overview)
- Network Encryption (TLS) (Conceptual overview)
- Enable Network Encryption using Single Domain
- Enable Network Encryption using Multiple Domains
- Enable Network Encryption using certmanager (Kubernetes only)
- Data Encryption (SSE) (Conceptual overview)
- Enable SSE using AIStor Key Management Server
- Enable SSE using KES (Summary page + linkouts)
- External Identity Management (Conceptual Overview)
- Enable External Identity management using OpenID
- Enable External Identity management using AD/LDAP
- Backup and Recovery
- Create a Multi-Site Replication Configuration
- Recovery after Hardware Failure
- Recover after drive failure
- Recover after node failure
- Recover after site failure
- Monitoring and Alerts
- Metrics and Alerting (v3 reference)
- Monitoring and Alerting using Prometheus
- Monitoring and Alerting using InfluxDB
- Monitoring and Alerting using Grafana
- Metrics V2 Reference
- Publish Server and Audit Logs to External Services
- MinIO Healthcheck API
The Administration, Developer, and Reference sections will remain as-is
for now.
http://192.241.195.202:9000/staging/singleplat/mindocs/index.html
# Goals
Maintaining multiple platforms is getting to be too much, and based on
analytics the actual number of users taking advantage of it is minimal.
Furthermore, the majority of traffic is to installation pages.
Therefore we're going to try to collapse back into a single MinIO Object
Storage product, and use simple navigation and on-page selectors to
handle Baremetal vs Kubernetes.
This may also help to eventually stage us to migrate to Hugo + Markdown
---------
Co-authored-by: Daryl White <53910321+djwfyi@users.noreply.github.com>
Co-authored-by: Rushan <rushenn@minio.io>
Co-authored-by: rushenn <rushenn123@gmail.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.
|