Skip to Main Content Documentation Home MySQL 8.0 Reference Manual Related Documentation MySQL 8.0 Release Notes MySQ...

class Gem::Package::TarHeader: A header for a tar file

class Gem::Package::TarInvalidError: Raised when a tar file is corrupt

class Gem::RequestSet::Lockfile::ParseError: Raised when a lockfile cannot be parsed

Skip to Main Content Documentation Home MySQL 8.0 Reference Manual Related Documentation MySQL 8.0 Release Notes MySQ...

Skip to Main Content Documentation Home MySQL 8.0 Reference Manual Related Documentation MySQL 8.0 Release Notes MySQ...

You can configure MinIO AIStor behavior by setting environment variables using the ObjectStore custom resource. The Operator writes these variables to a configuration file accessible by all MinIO AIStor Pods in the object store. Overview Version changed Support for valueFrom with configMapKeyRef and secretKeyRef requires Operator version RELEASE.2025-10-16T16-46-38Z or later. The Operator supports two methods for setting environment variables:

class Gem::MissingSpecVersionError: Raised when trying to activate a gem, and the gem exists on the system, but not the requested version. LoadError to catch all types of load errors.

class Gem::RemoteSourceException: Represents an error communicating via HTTP.

This page covers settings for connecting MinIO AIStor to an external etcd cluster. Etcd provides a distributed key-value store used for DNS-based bucket routing with virtual-host-style access. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, MinIO AIStor uses the environment variable value.