couchbase.com/v2
·  Namespaced Resource 
 CouchbaseScopeGroup
        CouchbaseScopeGroup represents a logical unit of data storage that sits between buckets and
collections e.g. a bucket may contain multiple scopes, and a scope may contain multiple
collections.  At present, scopes are not nested, so provide only a single level of
abstraction.  Scopes provide a coarser grained basis for role-based access control (RBAC)
and cross-datacenter replication (XDCR) than collections, but finer that buckets.
In order to be considered by the Operator, a scope must be referenced by either a
`CouchbaseBucket` or `CouchbaseEphemeralBucket` resource.
Unlike `CouchbaseScope` resources, scope groups represents multiple scopes, with the same
common set of collections, to be expressed as a single resource, minimizing required
configuration and Kubernetes API traffic.  It also forms the basis of Couchbase RBAC
security boundaries.
       Click on Property Name to show the description, and Pink Types to expand schema.
Required properties are marked with *
Change History
Couchbase Operator 2.8.1
Couchbase Operator 2.8.0
Couchbase Operator 2.7.0
~4
4 properties have changed the description
- .apiVersion
- .kind
- .spec.collections
- .spec.names
Couchbase Operator 2.6.4
Couchbase Operator 2.6.3
Couchbase Operator 2.6.2
Couchbase Operator 2.6.1
Couchbase Operator 2.6.0
Couchbase Operator 2.5.2
Couchbase Operator 2.5.1
~1
1 property has changed the description
- .spec.collections.selector
Couchbase Operator 2.5.0
~1
1 property has changed the description
- .spec.collections.selector
Couchbase Operator 2.4.3
~1
1 property has changed the description
- .spec.collections.selector
Couchbase Operator 2.4.2
Couchbase Operator 2.4.1
We don't have any examples of CouchbaseScopeGroup yet 😕
But the good news is, you can help us by contributing examples on GitHub
No links for CouchbaseScopeGroup yet
You can help us by adding useful links on GitHub
