Upgrading InfoScale

InfoScale provides enterprise-grade, persistent storage for Kubernetes and OpenShift environments, supporting both SAN and DAS architectures. It delivers high-availability features—including dynamic multipathing, FIPS-compliant encryption, and robust I/O fencing—to ensure data integrity for stateful applications. The solution is highly scalable, supporting multi-node clusters and cross-site disaster recovery through Volume Replicator (VVR).

Successful deployment and maintenance require rigorous adherence to prerequisites, including verifying support matrices, ensuring system resources, and resolving any existing cluster split-brain conditions. Before performing upgrades, administrators must validate the environment using the provided Pre-flight CLI and ensure all pending rollouts are complete. Upgrades follow a specific sequence: the InfoScale operator must be updated first, followed by the InfoScale cluster version via the Custom Resource (CR), and finally the underlying platform or OpenShift environment.

During platform upgrades, the cluster enters an "OS-Upgrade" state, transitioning back to "Running" once complete. Administrators should note key limitations, such as the inability to upgrade single-node clusters or those utilizing Flexible Storage Sharing (FSS). Proper management, including the use of valid license secrets and adherence to recommended node configuration (for example, non-schedulable master nodes), is essential for operational stability.