{"id":8289,"date":"2020-03-17T11:55:47","date_gmt":"2020-03-17T18:55:47","guid":{"rendered":"https:\/\/www.couchbase.com\/blog\/?p=8289"},"modified":"2025-06-13T21:33:38","modified_gmt":"2025-06-14T04:33:38","slug":"announcing-couchbase-autonomous-operator-2-0-beta","status":"publish","type":"post","link":"https:\/\/www.couchbase.com\/blog\/announcing-couchbase-autonomous-operator-2-0-beta\/","title":{"rendered":"Announcing Couchbase Autonomous Operator 2.0 Beta"},"content":{"rendered":"

Introducing Couchbase Autonomous Operator 2.0 Beta<\/h2>\n

Today, we are delighted to announce the latest preview of the Couchbase Autonomous Operator (CAO) 2.0 beta<\/b>. This release is a significant update to the Couchbase Autonomous Operator<\/b>.<\/p>\n

This release introduces several new enterprise-grade features with fully autonomous capabilities – security<\/b>, monitoring<\/b>, high-availability<\/b>, and manageability. <\/b>Many of our customers have been successfully running Couchbase Autonomous Operator in a production environment for the past year. Most of them engaged with us over the last 18 months to define<\/b> the requirements of Couchbase Autonomous Operator 2.0. Thank you so much!!<\/p>\n

Kubernetes at the Core with Advanced Capabilities<\/h2>\n

Couchbase Autonomous Operator 2.0 <\/b>builds on features in the Kubernetes platform 1.13+ at its core. In this release, we have re-architected how we install, upgrade, and manage, including Couchbase role-based access control (RBAC) security, cross datacenter replication (XDCR) management, monitoring through Prometheus, and scheduled backups. These advancements are based on many latest innovations in Couchbase Server and the improvement of the Kubernetes ecosystem with better support for custom resources.<\/p>\n

We hope you\u2019ll enjoy trying it out and let us know your feedback.<\/p>\n

What\u2019s New in Couchbase Autonomous Operator 2.0 Beta?<\/h2>\n

New Custom Resource Model<\/h3>\n

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 got separated into their custom resource types, which the Autonomous Operator aggregates together using label selection.<\/p>\n

Moving to this new model is crucial for the Autonomous Operator to be able to support future evolutions in the Kubernetes platform. You\u2019ll find that these changes also provide immediate advantages in terms of manageability. One of the most practical benefits is that you can achieve fine-grained access control over different parts of a Couchbase deployment through the enactment of custom resource role-based access control (RBAC).<\/p>\n

Autonomous Operator 2.0 requires that all Couchbase custom resources use the new format. Couchbase custom resources \u2014 such as CouchbaseCluster \u2013 are not backward compatible between Autonomous Operator versions 1 and 2. If you\u2019re upgrading from Autonomous Operator 1.x, a tool (cbopconv) has been provided to convert your existing CouchbaseCluster resources to version 2.0.<\/p>\n

User and RBAC Management<\/h3>\n

The Autonomous Operator can now directly manage the creation and authorization of Couchbase users (both local and LDAP). When combined with label selection, the new CouchbaseUser, CouchbaseGroup, and CouchbaseRoleBinding resources allow a great deal of flexibility in how the Autonomous Operator can manage users in multi-cluster deployments.<\/p>\n

Support for LDAP and RBAC is available starting with Couchbase Server 6.5.<\/p>\n

Backup Management<\/h3>\n

Backup is one of the most mundane and repetitive activities for a database administrator. However, it is an equally important task that cannot be ignored.<\/p>\n

Autonomous Operator 2.0 users of Couchbase will have a completely seamless automated\/scheduled backup experience with all the enterprise-grade functionality provided by Couchbase Server cbbackupmgr<\/i><\/a>. This also includes the ability to restore a backup to the Couchbase cluster using the CouchbaseBackupRestore resources definition.<\/p>\n

Prometheus Metrics Collection<\/h3>\n

Proactive monitoring and alerting is essential to managing a healthy Couchbase environment. While the Couchbase Web Console provides detailed statistics and alerting functionality, it is intended to be a realtime dashboard and does not tie into many of the other things a system operator may need to monitor. Integration with external monitoring systems such as Prometheus is required for two primary purposes: proactive alerting and real-time metrics gathering across multiple Couchbase clusters.<\/p>\n

The latest operator provides native integration with the Couchbase Prometheus Exporter for collecting and exposing Couchbase Server metrics. These exported metrics can be scraped by Prometheus and then visualized in tools like Grafana.<\/p>\n

Certificate Authentication using Mutual TLS Support<\/h3>\n

Mutual TLS (mTLS) authentication between Couchbase Server and SDK clients are now fully supported by this release. With this mode of operation, not only do clients verify that they are talking to a trusted entity, but the Couchbase Server instance can also establish trust in the client.<\/p>\n

XDCR Management<\/h3>\n

The Autonomous Operator can now directly manage Cross Data Center Replication (XDCR) using the new CouchbaseReplication resource.<\/p>\n

Tutorials on Couchbase Mobile Integration<\/h3>\n

We have improved our tutorials and best practices on deploying Couchbase Sync Gateway in Kubernetes alongside Autonomous Operator<\/span> managed Couchbase custom resources.<\/p>\n

Resources:<\/h5>\n