Skip to content

Commit e7f4a33

Browse files
Merge pull request #287404 from pjw711/pjw/clarify-ephemeral-storage-position
Clarify no support for ephemeral volumes
2 parents 1cc7940 + 6fcbb80 commit e7f4a33

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/operator-nexus/concepts-storage.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,9 @@ The storage appliance in an Azure Operator Nexus instance is represented as an A
2121

2222
The Azure Operator Nexus software Kubernetes stack offers two types of storage. Operators select them through the Kubernetes StorageClass mechanism.
2323

24+
> [!IMPORTANT]
25+
> Azure Operator Nexus does not support ephemeral volumes. Nexus recommends that the persistent volume storage mechanisms described in this document are used for all workload volumes as these provide the highest levels of performance and availability. All storage in Azure Operator Nexus is provided by the storage appliance. There is no support for storage provided by baremetal machine disks.
26+
2427
### StorageClass: nexus-volume
2528

2629
The default storage mechanism, *nexus-volume*, is the preferred choice for most users. It provides the highest levels of performance and availability. However, volumes can't be simultaneously shared across multiple worker nodes. Operators can access and manage these volumes by using the Azure API and portal, through the volume resource.

0 commit comments

Comments
 (0)