Concepts
Concepts help you to learn about the different parts of the NooBaa and the abstractions it uses.
This concept section is divided into the following modules:
What is NooBaa?
- Overview provides an introduction to NooBaa. It also gives an overview of the features it provides.
Declarative API
- NooBaa: This is the central CRD for a NooBaa deployment. It represents the entire NooBaa system and orchestrates all its components. Administrators interact with this resource to install, configure, and manage the NooBaa platform within a Kubernetes cluster.
- BackingStore: A
BackingStorerepresents underlying storage resources that NooBaa can use to store data. These can be cloud-based storage services (like AWS S3, Azure Blob Storage, or Google Cloud Storage) or on-premises storage systems (like a PV pool).BackingStores are used to create buckets and provide the physical storage layer. - NamespaceStore: A
NamespaceStoreis a special type ofBackingStorethat represents an entire external bucket or a prefix within a bucket. Instead of using the external storage as a backing for NooBaa’s own data services (like deduplication and compression), aNamespaceStoreprovides a direct, transparent connection to the external resource. This is useful for data federation and accessing existing data in place. - BucketClass: A
BucketClassdefines policies for how data is placed and managed across one or moreBackingStores. It can specify data placement policies like mirroring or spreading data across different stores. When a user requests a new bucket, they can specify aBucketClassto control the behavior and characteristics of their bucket. - ObjectBucketClaim: An
ObjectBucketClaim(OBC) is a Kubernetes-native way for a user or application to request a new object storage bucket, similar to how aPersistentVolumeClaim(PVC) requests block or file storage. When an OBC is created, the NooBaa operator provisions a correspondingObjectBucketand makes the connection details available to the application via aSecretand aConfigMap.







