diff --git a/docs/kubernetes/installation/k8s-storage-plane.md b/docs/kubernetes/installation/k8s-storage-plane.md index 479cdaa9..b7d7e154 100644 --- a/docs/kubernetes/installation/k8s-storage-plane.md +++ b/docs/kubernetes/installation/k8s-storage-plane.md @@ -119,7 +119,6 @@ metadata: namespace: simplyblock spec: clusterName: simplyblock-cluster - maxLogicalVolumeCount: 20 workerNodes: - worker-1.example.com - worker-2.example.com @@ -177,12 +176,12 @@ For a full list of configuration options see [Simplyblock Operator: StorageNodeS ## Create a Storage Pool -A storage pool is a grouping of logical volumes and capacity limits within the cluster. An initial `Pool` resource must +A storage pool is a grouping of logical volumes and capacity limits within the cluster. An initial `StoragePool` resource must be created to define a storage pool before being able to provision volumes. ```yaml title="storage-pool.yaml" apiVersion: storage.simplyblock.io/v1alpha1 -kind: Pool +kind: StoragePool metadata: name: production-pool namespace: simplyblock @@ -198,7 +197,7 @@ kubectl apply -f storage-pool.yaml The status of the storage pool can be checked with: ```bash title="Check the pool status" -kubectl get simplyblockpool -n simplyblock +kubectl get storagepools -n simplyblock ``` Once the pool is active, the operator automatically creates a StorageClass named diff --git a/docs/kubernetes/operations/scaling/expanding-storage-cluster.md b/docs/kubernetes/operations/scaling/expanding-storage-cluster.md index f50f4527..e5726748 100644 --- a/docs/kubernetes/operations/scaling/expanding-storage-cluster.md +++ b/docs/kubernetes/operations/scaling/expanding-storage-cluster.md @@ -56,9 +56,6 @@ metadata: spec: clusterName: simplyblock-cluster expand: true - maxLogicalVolumeCount: 20 - partitions: 0 - corePercentage: 50 workerNodes: - new-node-4.example.com - new-node-5.example.com @@ -75,9 +72,6 @@ metadata: spec: clusterName: simplyblock-cluster expand: true - maxLogicalVolumeCount: 20 - partitions: 0 - corePercentage: 50 workerNodes: - new-node-4.example.com - new-node-5.example.com @@ -104,7 +98,7 @@ kubectl get storagenodes -n simplyblock ### Option B: Add a Single Node via StorageNode CR -For cases that need per-node overrides (custom `maxLogicalVolumeCount`, `spdkSystemMemory`, etc.) or a +For cases that need per-node overrides (custom `spdkSystemMemory`, `failureDomain`, etc.) or a single node added manually, create a `StorageNode` CR directly. Set `overrides.expand: true` so the backend treats it as an expansion add rather than a fresh cluster node. @@ -123,7 +117,7 @@ spec: socketIndex: 0 overrides: expand: true - maxLogicalVolumeCount: 20 + spdkSystemMemory: "4G" ``` ```bash title="Apply the StorageNode CR" diff --git a/docs/reference/operator/index.md b/docs/reference/operator/index.md index 7a0cb307..f4f76f33 100644 --- a/docs/reference/operator/index.md +++ b/docs/reference/operator/index.md @@ -19,7 +19,7 @@ The operator manages the following Custom Resource Definitions (CRDs): | [`StorageNodeSet`](reference.md#storagenodeset) | - | Fleet-level declarative management of storage nodes across workers | | [`StorageNode`](reference.md#storagenode) | - | Represents a single backend storage node instance (auto-created) | | [`StorageNodeOps`](reference.md#storagenodeops) | - | One-shot operational action targeting a single storage node | -| [`Pool`](reference.md#storagepool) | - | Creates and manages storage pools | +| [`StoragePool`](reference.md#storagepool) | - | Creates and manages storage pools | | [`Task`](reference.md#task) | - | Monitors cluster tasks and their status | | [`StorageBackup`](reference.md#storagebackup) | - | Creates a one-time backup of a PVC to S3 | | [`BackupRestore`](reference.md#backuprestore) | - | Restores a backup into a new PVC | @@ -292,13 +292,13 @@ See [Pinned Volume Migration During Node Removal](../../kubernetes/operations/no ## Storage Pool -The `Pool` resource creates and manages storage pools. When a pool becomes active, the operator automatically +The `StoragePool` resource creates and manages storage pools. When a pool becomes active, the operator automatically creates a Kubernetes `StorageClass` named `simplyblock---`. The StorageClass is deleted when the pool is deleted. ```yaml title="Example: Create a storage pool" apiVersion: storage.simplyblock.io/v1alpha1 -kind: Pool +kind: StoragePool metadata: name: production-pool namespace: simplyblock @@ -313,11 +313,11 @@ spec: write: 1024 ``` -The complete set of `Pool` fields is available in [Pool reference](reference.md#storagepool). +The complete set of `StoragePool` fields is available in [StoragePool reference](reference.md#storagepool). ### Auto-Created StorageClass -The pool identifier is the `Pool` resource name (`metadata.name`). The operator uses that name as the backend pool +The pool identifier is the `StoragePool` resource name (`metadata.name`). The operator uses that name as the backend pool name and as the `pool_name` CSI StorageClass parameter. When the pool reaches an active state, the operator creates a `StorageClass` with: