Skip to content

Commit 84e4005

Browse files
Merge pull request #299385 from pjw711/pjw/ephemeral-fix
Fix description of ephemeral volume support
2 parents 7a0081e + 82fa794 commit 84e4005

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

articles/operator-nexus/concepts-storage-kubernetes.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Azure Operator Nexus storage for Kubernetes
2+
title: Azure Operator Nexus persistent storage for Kubernetes
33
description: Get an overview of available storage classes for Kubernetes on Azure Operator Nexus.
44
author: pjw711
55
ms.author: peterwhiting
@@ -9,13 +9,10 @@ ms.date: 01/06/2025
99
ms.custom: template-concept
1010
---
1111

12-
# Azure Operator Nexus storage for Kubernetes
12+
# Azure Operator Nexus persistent storage for Kubernetes
1313

1414
Each Azure Operator Nexus provides two types of persistent storage to Nexus Kubernetes cluster tenant workloads: *nexus-volume* and *nexus-shared*. Operators select the type of storage they need by creating Persistent Volume Claims (PVCs) using the *nexus-volume* or *nexus-shared* storage class. All data stored in persistent volumes is stored on a storage appliance deployed on-premises as part of the Azure Operator Nexus instance. Azure Operator Nexus requires one storage appliance and supports up to two storage appliances per Azure Operator Nexus instance.
1515

16-
> [!IMPORTANT]
17-
> Azure Operator Nexus doesn't support ephemeral volumes. Nexus recommends that the persistent volume storage mechanisms described in this document are used for all Nexus Kubernetes cluster workload volumes as these mechanisms provide the highest levels of performance and availability. All storage in Azure Operator Nexus is provided by the storage appliance. There's no support for storage provided by baremetal machine disks.
18-
1916
## Kubernetes storage classes
2017

2118
### StorageClass: nexus-volume
@@ -312,4 +309,8 @@ PVCs created using the nexus-volume and nexus-shared have minimum and maximum cl
312309
- A nexus-volume PVC provisioning request fails if the requested size is less than the minimum or more than the maximum supported volume size.
313310
- Nexus-shared volumes are logically thin-provisioned on the backing NFS server. This NFS server has a fixed capacity of 1 TiB.
314311
- A nexus-shared PVC can be provisioned despite requesting more than 1 TiB of storage, however, only 1 TiB can be consumed.
315-
- It's possible to provision a set of PVCs where the sum of capacity requests is greater than 1 TiB. However, the consumption limit of 1 TiB applies; the set of associated PVs can't consume more than 1 TiB of storage.
312+
- It's possible to provision a set of PVCs where the sum of capacity requests is greater than 1 TiB. However, the consumption limit of 1 TiB applies; the set of associated PVs can't consume more than 1 TiB of storage.
313+
314+
## Limitations
315+
316+
- Azure Operator Nexus does not support [CSI ephemeral volumes](https://kubernetes.io/docs/concepts/storage/ephemeral-volumes/#csi-ephemeral-volumes).

0 commit comments

Comments
 (0)