Learn how to manage company members in the Docker Admin Console.

Learn how to manage settings for organizations using Docker Admin Console.

Learn how to create and manage teams for your organization

This procedure deploys MinIO AIStor on Kubernetes clusters using a private container registry for images while installing Helm charts from the public MinIO Helm repository. Use this procedure when your environment has internet access to install Helm charts from helm.min.io but you need to pull container images from a private container registry instead of the public quay.io registry. This procedure requires installation of Kubernetes operators and associated resources including CustomResourceDefinitions, StatefulSets, and Secrets into new or existing Namespaces. You must perform the operations in this procedure as a user that has broad permissions to create resources within multiple Namespaces.

Configure load balancers and reverse proxies for MinIO AIStor on Linux. Includes example configurations for NGINX and HAProxy.

This procedure explains how to specify the TLS certificates your MinIO AIStor deployment requires and configure your deployment to work with the certificates. See also Enable Network Encryption for explanations of how MinIO AIStor requires TLS and which cipher suites MinIO AIStor supports. Prerequisites The appropriate X.509 certificates for your environment.

This section documents steps for running MinIO AIStor as a container. Procedure Pull the latest stable image of AIStor Server Docker docker pull quay.io/minio/aistor/minio Podman podman pull quay.io/minio/aistor/minio Create the directory structure Create directories for data and certificates. The following example uses $HOME/minio as the base path.

MinIO AIStor implements Transport Layer Security (TLS) 1.2+ encryption with support for Server Name Indication (SNI) for selecting relevant TLS certificates in response to client requests. MinIO AIStor supports two types of certificate management: Automatic TLS certificate provisioning (default) User-provided TLS certificates When deploying an MinIO AIStor resource, the CRD definition provides a certificates field for controlling certificate generation and behavior. This field is also available in the object store Helm chart.

This page documents the installation and management of MinIO AIStor object storage using MinIO’s Red Hat OpenShift-certified operator through the Red Hat OLM. If you prefer to install on OpenShift using regular Helm charts, use the regular install instructions. This procedure assumes that the user interacting with the OpenShift cluster has authorization to: Install Kubernetes operators and associated resources including CustomResourceDefinitions, StatefulSets, and Secrets into new or existing Namespaces. Perform operations as a user that has broad permissions to create resources within multiple Namespaces. Install the MinIO AIStor Operator This section installs the OpenShift-certified MinIO AIStor Operator. You must complete this section before proceeding to deploying MinIO AIStor.

This page explains how to deploy MinIO AIStor with KES for Server Side Encryption. For instructions on running KES, see the KES docs. Broadly, the required steps are: Create a new external key (EK) for server-side encryption (SSE). Create or modify an MinIO AIStor deployment to support SSE with KES. Configure automatic bucket-default SSE. Enabling SSE on an MinIO AIStor deployment automatically encrypts the backend data for that deployment using the default encryption key.