Upgrade AIStor on Kubernetes (Helm)

AIStor Helm installations consist of two primary parts:

• The operator chart that controls resources like CustomResourceDefinitions
• The object-store chart that deploys the AIStor Server

You can also upgrade only the AIStor Server image used by a given chart.

This page documents a procedure for all three upgrade paths.

Upgrading charts or images may trigger the restart or deletion of resources, including the AIStor pods themselves. The AIStor Operator re-creates and starts pods with total cluster availability within milliseconds to seconds. However, some Kubernetes subsystems such as DNS may create additional delays in availability by up to 30 seconds. S3 SDKs and applications typically implement retry mechanisms that mitigate the impact of any reduced availability.

The AIStor Server Operator chart provides the core resources necessary for deploying AIStor Server onto Kubernetes infrastructure. Upgrading the chart brings in new changes to the operator resources, such as new features, capabilities, or updates to the underlying CustomResourceDefinition.

Before upgrading the chart, do the following:

• Review the upgrade prerequisites
• Take a backup of the existing Helm configuration using the helm get values command.

1. Verify the existing installation

   Use the kubectl get all -n aistor-operator command to verify the health and status of all pods and services in the namespace.

2. Update the AIStor Helm repository

   Use the helm repo update command to update the repository for the latest charts:

   helm repo update minio
   

3. Upgrade the Operator chart

   Use the helm upgrade command to upgrade the operator chart:

   helm upgrade -n aistor operator minio/aistor-objectstore-operator
   

4. Validate the upgrade

   You can check the operator pods in the aistor namespace to confirm the Helm upgrade deployed correctly.

   kubectl get all -n aistor-operator
   

The AIStor Server chart deploys object storage resources onto Kubernetes infrastructure. Upgrading the chart brings in new changes to the object store, such as features, capabilities, or updated AIStor server binaries.

Before upgrading the chart, do the following:

• Review the upgrade prerequisites
• Take a backup of the existing Helm configuration using the helm get values command.

1. Verify the existing installation

   Use the kubectl get all -n OBJECT-STORE-NAMESPACE command to verify the health and status of all pods and services in the namespace.

2. Update the AIStor Helm repository

   Use the helm repo update command to update the repository for the latest charts:

   helm repo update minio
   

3. Upgrade the object store chart

   Use the helm upgrade command to upgrade the aistor-objectstore chart. You must pass in the existing chart values to ensure your customized settings override any defaults set as part of the chart upgrade.

   helm upgrade -n OBJECT-STORE-NAMESPACE object-store-name minio/aistor-objectstore -f object-store-values.yaml
   

4. Validate the upgrade

   You can check the pods in the object store namespace to confirm the Helm upgrade deployed correctly.

   kubectl get all -n OBJECT-STORE-NAMESPACE
   

You can upgrade the AIStor Server version in a given object store deployment by specifying a new image to the Chart.

1. Update the object store values.yaml

   Open the object-store-values.yaml file in your preferred text editor. The objectStore.image field controls the specific image tag used by the deployment.

   Update the value to your target new release tag. The following example uses the latest stable release of AIStor server.

   objectStore:
      image:
         repository: quay.io/minio/aistor/minio
         tag: RELEASE.2025-05-30T11-03-39Z
   

2. Upgrade the object store chart

   Use the helm upgrade command to upgrade the object-store chart. You must pass in the existing chart values to ensure your customized settings override any defaults set as part of the chart upgrade.

   helm upgrade -n OBJECT-STORE-NAMESPACE object-store-name minio/aistor-objectstore -f object-store-values.yaml
   

3. Validate the upgrade

   You can check the pods in the object store namespace to confirm the Helm upgrade deployed correctly.

   kubectl get all -n OBJECT-STORE-NAMESPACE