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>
4.5 KiB
Installation and Management
minio
Table of Contents
This section documents steps for installing and managing the
AGPLv3-licensed Community MinIO Object Storage on Kubernetes <minio-kubernetes> and Baremetal <minio-baremetal> infrastructures.
MinIO is a software-defined high performance distributed object storage server. You can run MinIO on consumer or enterprise-grade hardware and a variety of operating systems and architectures.
All MinIO deployments implement Erasure Coding <minio-erasure-coding> backends.
You can deploy MinIO using one of the following topologies:
Single-Node Single-Drive <minio-snsd>(SNSD or "Standalone")-
Local development and evaluation with no/limited reliability
Single-Node Multi-Drive <minio-snmd>(SNMD or "Standalone Multi-Drive")-
Workloads with lower performance, scale, and capacity requirements
Drive-level reliability with configurable tolerance for loss of up to 1/2 all drives
Evaluation of multi-drive topologies and failover behavior.
Multi-Node Multi-Drive <minio-mnmd>(MNMD or "Distributed")-
Enterprise-grade high-performance object storage
Multi Node/Drive level reliability with configurable tolerance for loss of up to 1/2 all nodes/drives
Primary storage for AI/ML, Distributed Query, Analytics, and other Data Lake components
Scalable for Petabyte+ workloads - both storage capacity and performance
Kubernetes
MinIO provides a Kubernetes-native Operator framework for managing and deploying Tenants onto your managed infrastructure.
MinIO fully supports upstream Kubernetes and most flavors which inherit from the upstream as a base. This includes, but is not limited to, RedHat Openshift, SUSE Rancher, VMWare Tanzu. MinIO also fully supports cloud-based Kubernetes engines such as Elastic Kubernetes Engine, Google Kubernetes Service, and Azure Kubernetes Service.
Select the link most appropriate for your Kubernetes infrastructure. If your provider is not listed, use the Kubernetes Upstream documentation as a baseline and modify as needed based on your provider's guidance or divergence from upstream semantics and behavior.
Deploy MinIO on Kubernetes (Upstream) <deploy-operator-kubernetes>Deploy MinIO on Openshift Kubernetes <deploy-operator-openshift>Deploy MinIO on SUSE Rancher Kubernetes <deploy-operator-rancher>Deploy MinIO on Elastic Kubernetes Service <deploy-operator-eks>Deploy MinIO on Google Kubernetes Engine <deploy-operator-gke>Deploy MinIO on Azure Kubernetes Service <deploy-operator-aks>
Baremetal
MinIO supports deploying onto baremetal infrastructure - physical machines or virtualized hosts - running Linux, MacOS, and Windows. You can also deploy MinIO as a container onto supported Operating Systems.
Deploy MinIO onto RedHat Linux <deploy-minio-rhel>Deploy MinIO onto Ubuntu Linux <deploy-minio-ubuntu>Deploy MinIO as a Container <deploy-minio-container>Deploy MinIO onto MacOS <deploy-minio-macos>Deploy MinIO onto Windows <deploy-minio-windows>
Important
MinIO strongly recommends Linux (RHEL, Ubuntu) <minio/linux/index.html>
or Kubernetes (Upstream, OpenShift) <minio/kubernetes/upstream/index.html>
for long-term development and production environments.
MinIO provides no guarantee of support for SNMD (Single-Node Multi-Drive) or MNMD (Multi-Node Multi-Drive) topologies on MacOS,
Windows, or Containerized deployments.
/operations/deployments/kubernetes /operations/deployments/baremetal