## Updates for `console` early Dec22 releases - Updated the instructions for registering for SUBNET from an airgapped Console environment - Minor typo in IAM doc. Closes #664 Two of the items in that issue did not actually impact the docs. One item is just a screenshot update that will be addressed later. ## Updates for `minio` early Dec22 releases - Adds info about `mc` installed with container images - Adds new envvar for KES enclaves Closes #665 - Updates `mc support inspect` to correct alias to target in command syntax
2.8 KiB
Install and Deploy MinIO
minio
Table of Contents
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.
MinIO supports three deployment topologies:
- Single-Node Single-Drive (SNSD or "Standalone")
-
A single MinIO server with a single storage volume or folder. deployment provides failover protections. Drive-level reliability and failover depends on the underlying storage volume.
deployments are best suited for evaluation and initial development of applications using MinIO for object storage.
deployments implement a zero-parity erasure coding backend and include support for the following erasure-coding dependent features:
Versioning <minio-bucket-versioning>
Object Locking / Retention <minio-object-retention>
- Single-Node Multi-Drive (SNMD or "Standalone Multi-Drive")
-
A single MinIO server with four or more storage volumes. deployments provide drive-level reliability and failover only.
- Multi-Node Multi-Drive (MNMD or "Distributed")
-
Multiple MinIO servers with at least four drives across all servers. The distributed topology supports production-grade object storage with drive and node-level availability and resiliency.
This documentation provides instructions for and for supporting local development and evaluation of MinIO on a single host machine. For deployments, use the MinIO Kubernetes Operator to deploy and manage MinIO tenants in a containerized and orchestrated environment.
Platform Support
MinIO provides container images at the following repositories:
RELEASE.2022-12-02T19-19-22Z
These images include the MinIO Client <minio-client>
command line tool
built in for container-level debugging. However, to regularly interact
with a container MinIO install, install the MinIO Client <mc-install>
on your
computer and define an mc alias set <alias>
to the container
instead.
Use of MinIO images from any other repository, host, or organization is at your own risk.
The Single-Node Single-Drive <minio-snsd>
and Single-Node Multi-Drive <minio-snmd>
tutorials
provide instructions for the Docker and Podman <>
container managers.
/operations/install-deploy-manage/deploy-minio-single-node-single-drive /operations/install-deploy-manage/deploy-minio-single-node-multi-drive