You are viewing the documentation for a prerelease version.

View Latest

Release Notes for Couchbase Autonomous Operator 2.0

Couchbase Autonomous Operator 2.0 is a landmark release that’s built to take advantage of the latest Kubernetes improvements in the areas of security and custom resources. The changes in this release enable several advancements in how you can manage, monitor, and deploy Couchbase clusters.

Take a look at the What’s New page for a list of new features and improvements that are available in this release.

Release 2.0.0 Beta

Couchbase Autonomous Operator 2.0.0 Beta was released in March 2020.

Installation and Upgrade

For installation instructions, see Installing on Kubernetes and Installing on OpenShift.

For upgrade instructions, see Upgrading the Operator.

The Autonomous Operator 2.0.0 Beta is not production-ready software, and therefore upgrading from the Beta to the final GA version will not be supported. You should only install the Beta software in development environments for testing purposes.

Platform Support

For the latest platform support information, see Prerequisites.

New Platform Support

This release adds support for the following platforms:

  • Open Source Kubernetes 1.15

  • Red Hat OpenShift 4.2

Removed Platform Support:

This release drops support for the following platforms:

  • Couchbase Server 5.5

  • Red Hat OpenShift Container Platform 3.x

Major Behavior Changes

New Couchbase Custom Resource Model

As discussed on the What’s New page, this release introduces a new model for deploying and managing Couchbase custom resources. Previously, you would deploy a cluster using a single, monolithic CouchbaseCluster resource configuration that defined everything about a cluster (e.g. nodes, buckets, XDCR, etc). Starting with Autonomous Operator 2.0, parts of the CouchbaseCluster resource have been separated into their own custom resource types, which the Autonomous Operator aggregates together using label selection.

The available set of Couchbase custom resource types include:

Autonomous Operator 2.0 requires that all Couchbase custom resources use the new format. Couchbase custom resources — such as CouchbaseCluster -- are not backwards compatible between Autonomous Operator versions 1 and 2. If you’re upgrading from Autonomous Operator 1.x, a tool (cbopconv) has been provided in the standard Autonomous Operator download package to convert your existing CouchbaseCluster resources to version 2.

Read more about how to use the cbopconv tool in the upgrade documentation.

Installation Procedure

The documented installation procedures now take advantage of the cbopcfg tool for installing both the Dynamic Admission Controller and the Autonomous Operator. This tool greatly simplifies the installation process and accommodates most environments.

Read more about the cbopcfg tool, as well as Installing on Kubernetes and Installing on OpenShift.

If the cbopcfg tool doesn’t suit your environment, you can still manually install the Dynamic Admission Controller and Autonomous Operator using YAML configs:

Couchbase Pod Upgrades

The Autonomous Operator can now better handle certain configuration changes that require pods to be replaced. Some of these configuration changes include:

Read more about Couchbase Pod Upgrades.

Logging

The Autonomous Operator and Dynamic Admission Controller now use JSON logging. This change includes some helpful enhancements, such as pod status outputs no longer spanning multiple lines, and rebalance status now being labelled with proper cluster context.

Feedback

You can have a big impact on future versions of the Operator (and its documentation) by providing Couchbase with your direct feedback and observations. Please feel free to post your questions and comments to the Couchbase Forums.

Licenses for Third-Party Components

The complete list of licenses for Couchbase products is available on the Legal Agreements page. Couchbase is thankful to all of the individuals that have created these third-party components.

More Information