Skip to main content
Loading
Version: 2.2.0

Upgrade the Operator on OpenShift using Web Console from 2.1.0 to 2.2.0

Verify that 2.2.0 version of the operator is available

Launch OpenShift web console. Using the Administrator view, navigate to Operators > OperatorHub. Search for Aerospike. Select the Marketplace version of the Aerospike Kubernetes Operator as shown:

A dialog appears describing the Operator as shown below. You should see 2.2.0 as the latest version.

Upgrade the Operator

Based on the installPlanApproval mode, the upgrade of the Operator can be one of

  • Automatic - the default when installing the Operator from Red Hat Marketplace
  • Manual - if the Operator subscription has been edited to use Manual approval

Automatic

The standard install procedure sets up Automatic upgrade approval for the operator. In this case OpenShift automatically installs 2.2.0 version of the operator. You do not need any manual steps.

Check that operator has been upgraded using the Administrator view, navigate to Operators > Installed Operators. Search for Aerospike.

You should see that the Operator has been upgrade to version 2.2.0 as shown below.

You can skip ahead to configuring the CLI step.

Manual

If the Operator's subscription has been set to use Manual approval, during installation(or has been edited later on ) then you need to approve the upgrade manually.

Navigate to the operator the Administrator view, navigate to Operators > Installed Operators. Search for Aerospike.

You will see that the new Operator upgrade version 2.2.0 is available as shown below.

Click on Upgrade Available to start the upgrade which shows the details of the InstallPlan as follows:

info

The name of the InstallPlan is auto generated and can be different.

Click on Preview InstallPlan to which shows the details of the InstallPlan as follows:

Click on Approve button to approve the upgrade and begin the upgrade.

On successful upgrade, a message like the following appears:

Select View Operator to verify the Operator details. The following details appear:

Configure the CLI

From a terminal, login to the OpenShift cluster and ensure that the oc and kubectl commands connect to the correct OpenShift cluster.

Check Operator Logs

The Operator runs as two replicas by default, for higher availability. Run the following command to follow the logs for the Operator pods:

kubectl -n openshift-operators logs -f deployment/aerospike-operator-controller-manager manager

Sample output:

2022-06-16T19:09:58.058Z    INFO    controller-runtime.metrics  metrics server is starting to listen    {"addr": "127.0.0.1:8080"}
2022-06-16T19:09:58.062Z INFO setup Init aerospike-server config schemas

2022-06-16T19:09:58.071Z DEBUG schema-map Config schema added {"version": "4.7.0"}
2022-06-16T19:09:58.072Z INFO aerospikecluster-resource Registering mutating webhook to the webhook server
2022-06-16T19:09:58.073Z INFO controller-runtime.webhook registering webhook {"path": "/mutate-asdb-aerospike-com-v1beta1-aerospikecluster"}
2022-06-16T19:09:58.073Z INFO controller-runtime.builder skip registering a mutating webhook, admission.Defaulter interface is not implemented {"GVK": "asdb.aerospike.com/v1beta1, Kind=AerospikeCluster"}
2022-06-16T19:09:58.073Z INFO controller-runtime.builder Registering a validating webhook {"GVK": "asdb.aerospike.com/v1beta1, Kind=AerospikeCluster", "path": "/validate-asdb-aerospike-com-v1beta1-aerospikecluster"}
2022-06-16T19:09:58.073Z INFO controller-runtime.webhook registering webhook {"path": "/validate-asdb-aerospike-com-v1beta1-aerospikecluster"}
2022-06-16T19:09:58.074Z INFO setup Starting manager
I1015 19:09:58.074722 1 leaderelection.go:243] attempting to acquire leader lease aerospike/96242fdf.aerospike.com...

Grant RBAC permissions to non-aerospike Kubernetes namespaces

caution

There is a known issue in OLM based installations (OperatorHub.io and on Red Hat OpenShift) where upgrade to version 2.2.0 from 2.1.0, causes revoking of RBAC privileges required to run Aerospike clusters in Kubernetes namespaces other than the aerospike namespace.

If you are running Aerospike clusters in Kubernetes namespaces other than the aerospike namespace, re-grant the RBAC privileges following instructions here.