Upgrade Operator 2.5.0 to 3.0.0
Choose the upgrade method based on your Operator installation.
Operator versions starting with 2.0.0 can upgrade directly to versions 2.5.0 and earlier without going through the intermediate versions. For Upgrading Operator to 3.0.0, the operator must be on version 2.5.0.
Upgrade operator on an OLM installation
There is a known issue with upgrading from version 2.5.0 to 3.0.0. This upgrade scenario revokes the RBAC privileges required to run Aerospike clusters.
If you are upgrading from 2.5.0 to 3.0.0, follow these instructions to restore the required RBAC privileges for each Kubernetes namespace where Aerospike clusters are running.
The implementation on OpenShift upgrades sequentially through the intermediate versions after 2.5.0 version. The implementation on OperatorHub.io upgrades sequentially through the intermediate versions.
Upgrade operator on a Helm-based installation
Helm upgrades require manual user control. You can perform either a sequential upgrade through each intermediate version or directly upgrade to the newest version.