AIStor Operator Reference

The AIStor Operator manages AIStor Object Store deployments on Kubernetes clusters using the Kubernetes Operator pattern. The Operator automates deployment, configuration, and lifecycle management tasks for AIStor, reducing operational complexity when running on Kubernetes.

Use the AIStor Operator when deploying AIStor on Kubernetes platforms including upstream Kubernetes, Red Hat OpenShift, and other Kubernetes distributions. The Operator handles tasks such as pod scheduling, configuration management, certificate rotation, and upgrade orchestration.

Custom Resource Definitions

The Operator extends Kubernetes with Custom Resource Definitions (CRDs) that define AIStor-specific resources. Use these references to understand the available fields and configure your deployments.

You can also find complete examples of the values.yaml files for both the Operator and Object Store Helm charts. Use these to understand how you can customize object store deployments, Operator configuration options, setting precedence, networking configuration, ingress setup, resource management, and pod scheduling controls.

For improved fault tolerance across different failure domains, such as racks or availability zones, configure Spread Zones.

For information about configuring AIStor using environment variables, including how to securely reference values from Secrets and ConfigMaps, see Environment Variable Configuration.

The ObjectStore CRD (v1) provides the items for the API for production deployments.

The AdminJob CRD allows you to automate administrative tasks such as creating buckets, managing users and policies, and configuring object store settings through Kubernetes-native workflows.

Helm chart references

Install the AIStor Operator with Helm charts that support extensive customization options. These references document all available values for configuring deployments.

  • Operator Helm chart - Configure the Operator deployment, including resource limits, replicas, and service accounts
  • Object Store Helm chart - Configure Object Store deployments, including pool sizing, networking, ingress, and pod scheduling

Operator configuration

Configure Operator behavior through environment variables set on the Operator Deployment.

The Operator Environment Variables include options for TLS settings, namespace watching, and Prometheus integration.

Data protection

Protect Object Store data from accidental deletion.

  • PVC Protection - Prevent accidental PVC deletion by adding finalizers to Object Store PVCs

Next steps