Details
-
Bug
-
Resolution: Unresolved
-
Major
-
2.7.0
-
18 -Lost to Eternity
-
1
Description
As of Server 7.6, Collection-level maxTTL is now mutable, and also should also accept -1 to disable expiry.
As of CAO 2.7.0, maxTTL is mutable, but validation prevents setting to less than zero.
Assuming that no functional CRD change is required, we should address this in the next maintenance release.
Attachments
Issue Links
- relates to
-
K8S-3152 Per-collection maxTTL Changes
-
- Resolved
-
Gerrit Reviews
| For Gerrit Dashboard: K8S-3632 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 216408,2 | K8S-3632: Allow maxTTL to be -1 for collections | master | couchbase-operator | Status: NEW | 0 | +1 |