Release 3.4.1

Bug Fixes

• Fixed security vulnerabilities in the Aerospike Kubernetes Operator and Aerospike Kubernetes Init. [KO-365]

Release 3.4.0

New features

• Added support for Aerospike Database 7.2.x.x. [KO-352]
• Added compatibility with the Aerospike Backup Service to enable backup and restore functionality inside AKO. [KO-328]
• Integrated triggering warm and cold restarts on demand. [KO-211]
• Added a pause configuration option to pause cluster reconciliation. [KO-112]
• Made the init registry name in CR file configurable. [KO-338]
• Added an out-of-the-box monitoring stack implementation. [KO-344]

Improvements

• Increased default resource limit for AKO pods. [KO-271]

Full Changelog: 3.3.0...3.4.0

Release 3.3.1

Bug fixes

• Fix security vulnerabilities in the AKO. [KO-333]
• Fix security vulnerabilities in the AKO init. [KO-334]

Release 3.3.0

New Features

• Support Aerospike Database Enterprise Edition 7.1.X. [KO-318]
• Support default-password-file in Aerospike Database Enterprise Edition 7.1.X. [KO-326]
• Migrate pods from the given k8s nodes list. [KO-264]
• Enhance the operator to change the aerospike configs dynamically. [KO-293]
• Add Readiness probe and Pod Disruption Budget for server pods. [KO-198]

Improvements

• Allow to enable security in the deployed cluster. [KO-290]
• Optimize Aerospike Operator scale-down operation (Batch Scale Down). [KO-314]
• Allow load balancer service update. [KO-286]
• Add the AKO version in the CRD annotations. [KO-294]
• Add the AerospikeClusterPhase field in the AerospikeCluster status to represent the current phase of the Aerospike reconcile operation.
• Add the IsReadinessProbeEnabled field in the AerospikeCluster status to represent if the readiness probe is enabled for all the pods.

Bug fixes

• Change MultiPodPerHost type from bool to bool pointer. [KO-295]
• Allow to update read and write quotas in the user's role. [KO-327]

Release 3.2.2

What's Changed

• [KO-313] - Fix security vulnerabilities in all the components of the AKO
• Upgrade aerospike-management-lib which incorporate a fix for #272

Release 3.2.1

[KO-291] - Fix security vulnerabilities in all the components of the AKO

Release 3.2.0

New Features

• [KO -273] - Aerospike Server Enterprise version 7.0.x.x support.
• [KO -285] - Support for maxIgnorablePods to allow force Aerospike operations with failed pods in Operator.

Release 3.1.0

Improvements

• [KO -165] - Allow simultaneous scale down and rolling restart in the SC cluster.
• [KO -259] - Allow aerospike cluster migration from non-TLS to TLS or vice-versa.
• [KO -262] - Ability to use skipWorkDirValidate with the non-root aerospike cluster setup.

Release 3.0.0

New Features

• [KO -254] - Aerospike Server Enterprise version 6.4.x.x support.

Improvements

• [KO -132] - Support topology.kubernetes.io/zone key.
• [KO -190] - Remove unused files from bundle and helm-chart.
• [KO -218] - Aerospike Operator to support CA-Path along with CA-File.
• [KO -219] - Avoid unnecessary Kubernetes Service resource creation and Kubernetes node API calls.
• [KO -220] - Segregate Operator and AerospikeCluster RBAC.
• [KO -221] - Move to CRD v1 API and update the Operator release channel to stable.
• [KO -235] - Re-initialize the volume if the corresponding PVC has been recreated.

Bug fixes

• [K0 -229] - Operator unable to roll back specific fields causing un-schedulable state for Aerospike cluster Pods.
• [K0 -239] - LDAP not working with server images after 6.1.0.5.

Known Issues

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.

Release 2.5.0

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.