A newer version of this documentation is available.

View Latest

Release Notes


      Couchbase Autonomous Operator 1.0 provides the first native integration of Couchbase Server with Kubernetes platforms.

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

      Couchbase Autonomous Operator 1.0 was released in August 2018.

      Platform Support

      For the latest platform support information, see Prerequisites.

      Known Issues and Limitations

      Known Limitations
      • Upgrading Couchbase Server using the Operator is not currently supported.

      • The Operator manages the state of the Couchbase Server cluster. Therefore, at this time, all cluster configuration changes must be made by modifying the CouchbaseCluster configuration file and pushing it to Kubernetes. Any manual changes to the configuration that are made using the Couchbase Server Web Console, CLI, REST API, or SDK will be reverted by the Operator. This includes things like adding a node or creating a server group.

        The one exception is when disableBucketManagement is set to true in the CouchbaseCluster configuration (the default is false). If this is the case, the creation and deletion of Couchbase buckets must be done manually. Refer to the CouchbaseCluster documentation for more information.

      Table 1. Known Issues
      Issue Description


      Summary: Pod volumes are deleted when pods are deleted. As a result, important debugging information may not be available after a failure.


      Summary: cbopinfo does not redact potentially sensitive information from all logs.


      Summary: It’s not possible to attach a persistent volume to the Couchbase logs directory for deployments when Couchbase data is not written to a persistent volume. This means that important debugging information may be unavailable during failure situations.

      Workaround: You should always deploy Couchbase clusters in production with persistent volumes.


      Summary: Only dynamic volume provisioning via storage classes is supported.


      Summary: Kubernetes doesn’t allow the setting of ulimit parameters on individual containers.

      Workaround: You can set ulimits on the physical machine that Kubernetes is running on; the ulimit parameters will be inherited by the containers.


      Summary: When the same event occurs on different Couchbase nodes, the event order is not reported consistently. This may affect applications that rely on the event order to be consistent when checking the status of a Couchbase cluster.


      Summary: If a cluster is scaling up when not enough nodes are present, the Operator will not rebalance the cluster even if some nodes can be added.

      Workaround: You should ensure that sufficient resources are present in the Kubernetes cluster before scaling a Couchbase cluster.


      Summary: If you manually increase the number of replicas of a bucket, then the Operator may rebalance the cluster before reverting the bucket’s changes.

      Workaround: You should always change the CouchbaseCluster configuration through the Operator. If you change the CouchbaseCluster configuration directly on the cluster (such as through the Couchbase Server Web Console), then the Operator will revert those changes.


      Summary: In rare cases, Kubernetes can drop events that are logged by the Operator.


      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.