Autonomous Operator 2.4 release is primarily focused on adding some key features introduced in Couchbase Server 7.1 to Autonomous Operator such as support for ARM platforms and Encrypted Certificates, as well as other improvements related to TLS Certificate Management, cloud backups, index configuration, and the Prometheus Exporter.
Over the last few years, the ARM v8 processors which have generally been found in mobile devices, have gained popularity with both desktop hardware vendors and major Cloud Service providers.
In Couchbase Server 7.1.0 we added support for AWS Graviton-based instances, and since Couchbase Server 7.1.1 we have published multi-arch Docker container images supporting both
Now, with Autonomous Operator 2.4, all tools and container images for Open Source Kubernetes platforms are available for both architectures, allowing deployments on either
arm64 as well as migrations between the two.
|Support for ARM on the OpenShift Container Platform was added in Operator 2.4.2.
Couchbase Server 7.1 introduced support for Encrypted Private Keys, allowing administrators to use an encrypted private key using PKCS #5 v2 algorithms like AES 256.
Autonomous Operator 2.4 now exposes this feature, which prevents storing the TLS private key unencrypted anywhere on the system.
See TLS Passphrase Protection for further details.
This release adds several other improvements in the area of TLS Certificate Management.
With support for multiple Root CA’s in Server 7.1, certificates no longer need to be explicitly supplied for LDAP and instead can be placed inside the
RootCAs array. See tlsSecret
It is now possible to include multi-PEM CAs in the Server
Certificate Rotation has been expanded to allow plain text reload as a last resort in case of already-expired certificates. See Replacing expired Certificates
Relatedly, the Operator now raises Kubernetes Events when it detects TLS expiration.
Cloud Backup and Restore in Couchbase Server 7.1 now supports the use of Azure and GCP blob storage, and also adds the option to use an ephemeral volume for the staging directory. See Backup and Restore to a Cloud Store
Although the Exporter is no longer required when using Couchbase Server 7.x, which contains a native Prometheus endpoint, it may still be desirable to use the Couchbase Prometheus Exporter.
This release adds performance improvements and tuning options, see Configure Prometheus Metrics Collection for details.
In Kubernetes it is possible to use a local storage device (such as a disk, partition, or directory) as a Persistent Volume (see local).
From Couchbase Autonomous Operator 2.4.1, it is now possible to use these Local Volumes when deploying Couchbase Server resources. See Local Persistent Volumes for full details.