The storage-operator component is used to manage the lifecycle of storage components. This topic describes the features, usage notes, and release notes for storage-operator.

Introduction

Storage Operator is used to manage the lifecycle of storage components. Storage Operator runs as a Deployment, which deploys and upgrades storage components based on the default configurations inherited from the image and the custom configurations provided by ConfigMaps. This helps reduce the complexity of container development and maintenance.
  • Default configurations: Storage Operator provides the default configurations of storage components. The default configurations vary based on the version of Storage Operator.
  • Custom configurations: ConfigMaps can be used to define custom configurations of storage components, such as version information, and whether to install the component.
Storage Operator preferably uses custom configurations. The default configurations are used only when the custom configurations are not specified.
Storage-Operator
Note
  • Each image of Storage Operator contains the default configuration file.
  • When Storage Operator runs as a Deployment, the Deployment reads configurations from a ConfigMap file that is mounted on the Deployment and contains configurations of storage components.
  • Storage Operator determines whether to deploy and upgrade a storage component by combining the default and custom configurations.

Usage notes

For more information about how to deploy storage-operator from App Catalog, see Use Storage Operator to deploy and upgrade storage components.

Release notes

September 2021

Version Image address Release date Description Impact
v1.18.8.60-a5ba617-aliyun registry-vpc.${region}.aliyuncs.com/acs/storage-operator:v1.18.8.60-a5ba617-aliyun 2021-09-24
  • When Apsara File Storage NAS (NAS) file systems are managed by Container Network File System (CNFS), the Quota feature is enabled by default and automatic expansion is supported.
  • The issue that pods are scheduled to unavailable nodes is fixed.
  • Pods can be scheduled to Linux nodes and nodes other than the virtual-kubelet node.
  • The issue that the status of CNFS cannot be changed is fixed.
No impact on workloads

August 2021

Version Image address Release date Description Impact
v1.18.8.55-e398ce5-aliyun registry-vpc.${region}.aliyuncs.com/acs/storage-operator:v1.18.8.55-e398ce5-aliyun 2021-08-16
  • NAS file systems of the Capacity type can be created by using CNFS.
  • The archiveOnDelete parameter in the StorageClass automatically created by CNFS can be set to false. This way, the subdirectory mounted by a persistent volume (PV) is automatically deleted after you delete the PV.
  • The issue that storage-monitor occupies an excessive amount of CPU resources is fixed.
No impact on workloads

June 2021

Version Image address Release date Description Impact
v1.18.8.37-c63030b-aliyun registry-vpc.${region}.aliyuncs.com/acs/storage-operator:v1.18.8.37-c63030b-aliyun 2021-06-25
  • Automatic expansion is supported.
  • CNFS is supported.
No impact on workloads

March 2021

Version Image address Release date Description Impact
v1.18.8.28-18cca7b-aliyun registry-vpc.${region}.aliyuncs.com/acs/storage-operator:v1.18.8.28-18cca7b-aliyun 2021-03-25

New Features:

  • Batch snapshots are supported.
  • Scheduled snapshots are supported.
  • Cluster monitoring is supported.
No impact on workloads