Project documentation for Gluster Filesystem

Learn how to use Docker Engine SDKs to automate Docker tasks in your language of choice

<div class="flex h-full flex-col items-center justify-center text-center"><div class="mb-4 rounded-full bg-blue-100 p...

<div class="flex h-full flex-col items-center justify-center text-center"><div class="mb-4 rounded-full bg-blue-100 p...

The Test Report Aggregation Plugin version 9.2.1 Contents Usage Tasks Reports Dependency management The Test Report A...

This page describes how to enable FIPS 140-3 ready cryptography for AIStor deployments on Kubernetes. When enabled, FIPS mode restricts cryptographic operations to algorithms that align with the Federal Information Processing Standards (FIPS) 140-3 program. Organizations subject to U.S. federal government compliance requirements, or those with similar regulatory needs, may require FIPS-aligned cryptography. AIStor FIPS mode uses Go’s native cryptographic module, which restricts operations to FIPS 140-3 approved algorithms. MinIO makes no statements or representations regarding FIPS 140-3 certification status. Evaluate whether this implementation meets your specific compliance requirements. Overview AIStor uses Go 1.24’s native FIPS 140-3 cryptographic module. Enable FIPS mode at runtime with the GODEBUG environment variable. There is no separate binary required.

Configure load balancers and Ingress controllers for AIStor on Kubernetes. Includes examples for NGINX, HAProxy, and Traefik.

The Eclipse Plugins version 9.2.1 Contents Usage Tasks Configuration Customizing the generated files Separation of te...

The procedure on this page creates a new object lifecycle management rule that transitions objects from a bucket on a primary AIStor deployment to a bucket on a remote AIStor deployment. This procedure supports cost-management strategies such as tiering objects from a “hot” AIStor deployment using NVMe storage to a “warm” AIStor deployment using SSD. Requirements Install and configure mc This procedure uses mc for performing operations on the AIStor cluster. Install mc on a machine with network access to both source and destination clusters. See the mc Installation Quickstart for instructions on downloading and installing mc.

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. You must set up TLS before you can enable data encryption, also called server-side encryption. AIStor supports the following types of certificate signatures: self-signed internal or private certificate authorities (CAs) third-party CAs Multiple certificates are implemented with SNI to determine which certificate to return to a client based on the hostname in the request.