aerospike/aerospike-kubernetes-operator 2.5.0

Release 2.5.0

on GitHub

New Features

• [KO -191] - Aerospike Server Enterprise 6.3.x.x support
• [KO -130] - Allow Custom Interface in the CR NetworkPolicy.
• [KO -200] - Allow ConfiguredIP in the CR NetworkPolicy.

Improvements

• [KO -149] - Support custom Kubernetes cluster-domain.
• [KO -164] - Set migrate-fill-delay to the configured value before rolling restart.
• [KO -176] - Fix kube-rbac-proxy critical vulnerability in helm charts.

Bug fixes

• [K0 -166] - Race condition bug where spec might be updated in status without reconciling the CR.
• [K0 -192] - Fix init container permissions to allow this to run as non-root.
• [K0 -203] - CleanupThreads key not found crashing init container.
• [K0 -223] - Skip cluster-stable check for the removed namespace.

Known Issues

• Latest OLM (0.22.0) does not fully support ARM architecture.
• OLM-based installations (OperatorHub.io and on RedHat OpenShift) have a known issue with upgrading from version 2.4.0 to 2.5.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.4.0 to 2.5.0 and are running Aerospike clusters in Kubernetes namespaces other than the aerospike namespace, follow these instructions to restore the required RBAC privileges.