Upgrade Operator 2.2.1 to 2.3.0
Choose the upgrade method based on your Operator installation.
Operator versions starting with 2.0.0 can upgrade directly to the latest 2.x.0 version without going through the intermediate versions.
Upgrade operator on an OLM installation
OLM-based installations (OperatorHub.io and on Red Hat OpenShift) have a known issue with upgrading from version 2.2.1 to 2.3.0.
This upgrade scenario revokes the RBAC privileges required to run Aerospike clusters in Kubernetes namespaces other than the aerospike namespace.
If you are upgrading from 2.2.1 to 2.3.0 and are running Aerospike clusters in Kubernetes namespaces other than the aerospike namespace, follow these instructions to restore the required RBAC privileges.
The implementation on OpenShift upgrades to the newest version, skipping intermediate versions. 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.