CouchbaseCollectionGroup represent the finest grained size of data storage in Couchbase. Collections contain all documents and indexes in the system. Collections also form the finest grain basis for role-based access control (RBAC) and cross-datacenter replication (XDCR). In order to be considered by the Operator, every collection group must be referenced by a `CouchbaseScope` or `CouchbaseScopeGroup` resource. Unlike the CouchbaseCollection resource, a collection group represents multiple collections, with common configuration parameters, to be expressed as a single resource, minimizing required configuration and Kubernetes API traffic. It also forms the basis of Couchbase RBAC security boundaries.
4 top-level fields, 1 required · last changed in Couchbase Operator 2.7.1
APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
Spec defines the desired state of the resource.
MaxTTL defines how long a document is permitted to exist for, without modification, until it is automatically deleted. This field takes precedence over any TTL defined at the bucket level. This is a default, and maximum time-to-live and may be set to a lower value by the client. If the client specifies a higher value, then it is truncated to the maximum durability. Documents are removed by Couchbase, after they have expired, when either accessed, the expiry pager is run, or the bucket is compacted. When set to 0, then documents are not expired by default. This field must be a duration in the range 0-2147483648s, defaulting to 0. While this field can be changed on the CRD, it will not be updated on the collection if the Couchbase Server version is pre 7.6.0. More info: https://golang.org/pkg/time/#ParseDuration.
Names specifies the names of the collections. Unlike CouchbaseCollection, which specifies a single collection, a collection group specifies multiple, and the collection group must specify at least one collection name. Any collection names specified must be unique. Collection names must be 1-251 characters in length, contain only [a-zA-Z0-9_-%] and not start with either _ or %.
Source: couchbase.crds.yaml
Changes to CouchbaseCollectionGroup (couchbase.com/v2) in each Couchbase Operator version, compared to the version before it.
1 property has changed the description
Released · View CouchbaseCollectionGroup in 2.7.1
The description of CouchbaseCollectionGroup has changed
4 properties have changed the description
Released · View CouchbaseCollectionGroup in 2.7.0
CouchbaseCollectionGroup was already present in this version of Couchbase Operator, the oldest one on kubespec.dev
Released · View CouchbaseCollectionGroup in 2.3.1
No examples of CouchbaseCollectionGroup yet. Contribute one on GitHub.
kubespec.dev