Skip to content

README.md

Latest commit

 

History

History
34 lines (29 loc) · 2.66 KB

README.md

File metadata and controls

34 lines (29 loc) · 2.66 KB
title Readme
menu
docs_v2025.10.31
identifier name parent weight
readme-concepts
Readme
concepts
1
menu_name docs_v2025.10.31
section_menu_id concepts
url /docs/v2025.10.31/concepts/
aliases
/docs/v2025.10.31/concepts/README/
info
cli installer version
v0.20.0
v2025.10.31
v2025.10.31

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 BackingStore represents 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 NamespaceStore is a special type of BackingStore that 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), a NamespaceStore provides a direct, transparent connection to the external resource. This is useful for data federation and accessing existing data in place.
  • BucketClass: A BucketClass defines policies for how data is placed and managed across one or more BackingStores. It can specify data placement policies like mirroring or spreading data across different stores. When a user requests a new bucket, they can specify a BucketClass to 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 a PersistentVolumeClaim (PVC) requests block or file storage. When an OBC is created, the NooBaa operator provisions a corresponding ObjectBucket and makes the connection details available to the application via a Secret and a ConfigMap.