We’re happy to announce the release of Couchbase Autonomous Operator 1.1.0. As many of you know, version 1.0 which got released on August 30th was the first NoSQL production-ready Kubernetes operator for open source Kubernetes and Red Hat OpenShift.
Couchbase Autonomous Operator 1.1 introduces a number of supportability enhancements and bug fixes all based on critical feedback from our users.
Logs Support for Ephemeral Pods
To improve supportability in the case of Kubernetes node failure, the Operator now can persist just the Couchbase logs. By only persisting the log volumes, storage space is 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 specific 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.
Log Redaction and Extended Debugging
Logs collected with cbopinfo are automatically redacted of sensitive information by default. Also, 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.
Take a look at the release notes for a list of known and fixed issues in this release.
Here are some useful resources –
- Download Couchbase Autonomous Operator 1.1.0
- Read Couchbase Autonomous Operator 1.1.0 Documentation (What’s New)
- Share your thoughts on the Couchbase Forums