Couchbase Autonomous Operator 1.1 introduces a number of supportability features and enhancements. Take a look at the release notes for a list of known and fixed issues in this release.
To improve supportability in the case of Kubernetes node failure, the Operator now has the ability to persist just the Couchbase logs. By only persisting the log volumes, storage space can be used more efficiently. New options are also available to restrict the size and retention of logs.
This new functionality requires a persistent volume to be attached to Couchbase pods. To restrict the default volume mount to only persist the log subdirectory, add the
logs tag under
volumeMounts in the CouchbaseCluster configuration.
As a result of these changes, the Operator now supports certain stateless Couchbase node deployments in production, so long as persistent log volumes are attached to those pods. Review the best practices for more information about cluster supportability requirements.
Logs collected with cbopinfo are automatically redacted of sensitive information by default.
In addition, new options have been added to
cbopinfo to accommodate more environments and to be able to collect logs from volumes that are not attached to pods.