Docker extension API reference

Docker extension API reference

Stage names should be unique

Project documentation for Gluster Filesystem

Project documentation for Gluster Filesystem

Project documentation for Gluster Filesystem

Docs » Algorithms » Generalized Additive Models (GAM) Edit on GitHub Generalized Additive Models (GAM) Note : GAM mod...

This section documents steps for running 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 a data directory for use with the server

This page explains how to deploy 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 AIStor deployment to support SSE with KES. Configure automatic bucket-default SSE. Enabling SSE on an AIStor deployment automatically encrypts the backend data for that deployment using the default encryption key.

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. AIStor supports two types of certificate management: Automatic TLS certificate provisioning (default) User-provided TLS certificates When deploying an AIStor object store 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.