Skip to main content
Aerospike 8 introduces a new era of real-time transaction processingLearn more
Loading
Version: Operator 4.0.0

Upgrade AKO on Red Hat OpenShift

danger

AKO version 4.0.0 has breaking changes. Review the Breaking Changes before upgrading.

Aerospike Kubernetes Operator is a Red Hat Marketplace certified operator. It is available through the Red Hat certified operators catalog.

Upgrade AKO on your OpenShift cluster using the web console or command line:

OpenShift Web Console​

Use the following procedure to upgrade AKO installed on Red Hat OpenShift to the latest version using the web console.

note

If you are running an AKO version older than 3.4.x, you must first upgrade to the 3.4.x version before upgrading to 4.0.0.

Verify that AKO 4.0.0 is available​

  1. Launch the OpenShift web console.

  2. Using the Administrator view, go to Operators > OperatorHub.

  3. Search for Aerospike and select the Marketplace version of the Aerospike Kubernetes Operator:

    In the Marketplace Operator page, verify that 4.0.0 is the latest version.

Upgrade AKO​

Based on the installPlanApproval mode, the AKO upgrade is either:

  • Automatic: The default when installing AKO from Red Hat Marketplace.
  • Manual: If the Operator subscription has been edited to use Manual approval.

Automatic operator upgrade​

The standard install procedure sets up Automatic upgrade approval for the operator. In this case, OpenShift automatically installs the latest version. You do not need to perform any manual steps to upgrade, only to check that the upgrade was successful.

  1. Using the Administrator view, go to Operators > OperatorHub.

  2. Search for Aerospike.

    You should see that AKO has been upgraded to version 4.0.0, as shown below.

    Skip ahead to configuring the CLI.

Manual operator upgrade​

If the AKO subscription is set for Manual approval, follow these steps to manually approve the upgrade.

  1. In the OpenShift web console, go to the Administrator view.

  2. Go to Operators > Installed Operators.

  3. Search for Aerospike.

    You will see that the new AKO version is available, as shown below.

  4. Click on Upgrade Available to review the details of the InstallPlan:

    info

    The name of the InstallPlan is generated automatically and may be different from what is displayed in the following examples.

  5. Click on Preview InstallPlan to display the details of the InstallPlan:

  6. Click on Approve to approve and start the upgrade.

    The following message appears after a successful upgrade:

  7. Select View Operator to verify AKO details. The following details appear:

Configure the CLI​

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

Check AKO logs​

AKO runs as two replicas by default for higher availability. Run the following command to follow the logs for the AKO pods.

kubectl -n openshift-operators logs -f deployment/aerospike-operator-controller-manager manager
Sample output:
2025-02-04T07:59:36Z    INFO    setup   Initializing webhook certificate watcher using provided certificates    {"webhook-cert-path": "/tmp/k8s-webhook-server/serving-certs", "webhook-cert-name": "tls.crt", "webhook-cert-key": "tls.key"}
2025-02-04T07:59:36Z    INFO    controller-runtime.certwatcher  Updated current TLS certificate
2025-02-04T07:59:36Z    INFO    setup   Init aerospike-server config schemas
2025-02-04T07:59:36Z    DEBUG   setup   Config schema added {"version": "6.3.0"}
2025-02-04T07:59:36Z    DEBUG   setup   Config schema added {"version": "6.4.0"}
2025-02-04T07:59:36Z    DEBUG   setup   Config schema added {"version": "7.0.0"}
2025-02-04T07:59:36Z    DEBUG   setup   Config schema added {"version": "7.1.0"}
2025-02-04T07:59:36Z    DEBUG   setup   Config schema added {"version": "7.2.0"}
2025-02-04T07:59:36Z    DEBUG   setup   Config schema added {"version": "6.0.0"}
2025-02-04T07:59:36Z    DEBUG   setup   Config schema added {"version": "6.1.0"}
2025-02-04T07:59:36Z    DEBUG   setup   Config schema added {"version": "6.2.0"}
2025-02-04T07:59:36Z    DEBUG   setup   Config schema added {"version": "8.0.0"}
2025-02-04T07:59:36Z    INFO    controller-runtime.builder  Registering a mutating webhook  {"GVK": "asdb.aerospike.com/v1, Kind=AerospikeCluster", "path": "/mutate-asdb-aerospike-com-v1-aerospikecluster"}
2025-02-04T07:59:36Z    INFO    controller-runtime.webhook  Registering webhook {"path": "/mutate-asdb-aerospike-com-v1-aerospikecluster"}
2025-02-04T07:59:36Z    INFO    controller-runtime.builder  Registering a validating webhook    {"GVK": "asdb.aerospike.com/v1, Kind=AerospikeCluster", "path": "/validate-asdb-aerospike-com-v1-aerospikecluster"}
2025-02-04T07:59:36Z    INFO    controller-runtime.webhook  Registering webhook {"path": "/validate-asdb-aerospike-com-v1-aerospikecluster"}
2025-02-04T07:59:36Z    INFO    controller-runtime.builder  Registering a mutating webhook  {"GVK": "asdb.aerospike.com/v1beta1, Kind=AerospikeBackupService", "path": "/mutate-asdb-aerospike-com-v1beta1-aerospikebackupservice"}
2025-02-04T07:59:36Z    INFO    controller-runtime.webhook  Registering webhook {"path": "/mutate-asdb-aerospike-com-v1beta1-aerospikebackupservice"}
2025-02-04T07:59:36Z    INFO    controller-runtime.builder  Registering a validating webhook    {"GVK": "asdb.aerospike.com/v1beta1, Kind=AerospikeBackupService", "path": "/validate-asdb-aerospike-com-v1beta1-aerospikebackupservice"}
2025-02-04T07:59:36Z    INFO    controller-runtime.webhook  Registering webhook {"path": "/validate-asdb-aerospike-com-v1beta1-aerospikebackupservice"}
2025-02-04T07:59:36Z    INFO    controller-runtime.builder  Registering a mutating webhook  {"GVK": "asdb.aerospike.com/v1beta1, Kind=AerospikeBackup", "path": "/mutate-asdb-aerospike-com-v1beta1-aerospikebackup"}
2025-02-04T07:59:36Z    INFO    controller-runtime.webhook  Registering webhook {"path": "/mutate-asdb-aerospike-com-v1beta1-aerospikebackup"}
2025-02-04T07:59:36Z    INFO    controller-runtime.builder  Registering a validating webhook    {"GVK": "asdb.aerospike.com/v1beta1, Kind=AerospikeBackup", "path": "/validate-asdb-aerospike-com-v1beta1-aerospikebackup"}
2025-02-04T07:59:36Z    INFO    controller-runtime.webhook  Registering webhook {"path": "/validate-asdb-aerospike-com-v1beta1-aerospikebackup"}
2025-02-04T07:59:36Z    INFO    controller-runtime.builder  Registering a mutating webhook  {"GVK": "asdb.aerospike.com/v1beta1, Kind=AerospikeRestore", "path": "/mutate-asdb-aerospike-com-v1beta1-aerospikerestore"}
2025-02-04T07:59:36Z    INFO    controller-runtime.webhook  Registering webhook {"path": "/mutate-asdb-aerospike-com-v1beta1-aerospikerestore"}
2025-02-04T07:59:36Z    INFO    controller-runtime.builder  Registering a validating webhook    {"GVK": "asdb.aerospike.com/v1beta1, Kind=AerospikeRestore", "path": "/validate-asdb-aerospike-com-v1beta1-aerospikerestore"}
2025-02-04T07:59:36Z    INFO    controller-runtime.webhook  Registering webhook {"path": "/validate-asdb-aerospike-com-v1beta1-aerospikerestore"}
2025-02-04T07:59:36Z    INFO    setup   Adding webhook certificate watcher to manager
2025-02-04T07:59:36Z    INFO    setup   Starting manager
2025-02-04T07:59:36Z    INFO    controller-runtime.metrics  Starting metrics server
2025-02-04T07:59:36Z    INFO    setup   disabling http/2
2025-02-04T07:59:36Z    INFO    starting server {"name": "health probe", "addr": "[::]:8081"}
2025-02-04T07:59:36Z    INFO    controller-runtime.webhook  Starting webhook server
2025-02-04T07:59:36Z    INFO    setup   disabling http/2
2025-02-04T07:59:36Z    INFO    controller-runtime.webhook  Serving webhook server  {"host": "", "port": 9443}
Last updated on