Skip to content

Commit f6b59a6

Browse files
Merge pull request #253355 from neilverse/main
Main
2 parents 1c1d0af + fe3d34d commit f6b59a6

File tree

1 file changed

+80
-1
lines changed

1 file changed

+80
-1
lines changed

articles/operator-nexus/concepts-storage.md

Lines changed: 80 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,12 +25,91 @@ The Azure Operator Nexus software Kubernetes stack offers two types of storage.
2525

2626
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.
2727

28+
```
29+
apiVersion: v1
30+
kind: PersistentVolumeClaim
31+
metadata:
32+
name: testPvc
33+
namespace: default
34+
spec:
35+
accessModes:
36+
- ReadWriteOnce
37+
resources:
38+
requests:
39+
storage: 107Mi
40+
storageClassName: nexus-volume
41+
volumeMode: Filesystem
42+
volumeName: testVolume
43+
status:
44+
accessModes:
45+
- ReadWriteOnce
46+
capacity:
47+
storage: 107Mi
48+
phase: Bound
49+
```
50+
2851
### StorageClass: nexus-shared
2952

30-
In situations where a shared file system is required, the *nexus-shared* storage class is available. This storage class provides a shared storage solution by enabling multiple pods to concurrently access and share the same volume.
53+
In situations where a shared file system is required, the *nexus-shared* storage class is available. This storage class provides a shared storage solution by enabling multiple pods to concurrently access and share the same volume. These volumes are of type NFS Storage that are accessed by the kubernetes nodes as a persistent volume. Nexus-shared supports both Read Write Once (RWO) and Read Write Many (RWX) access modes. What that means is that the workload applications can make use of either of these access modes to access the storage.
3154

3255
Although the performance and availability of *nexus-shared* are sufficient for most applications, we recommend that workloads with heavy I/O requirements use the *nexus-volume* option for optimal performance.
3356

57+
#### Read Write Once (RWO)
58+
59+
In Read Write Once (RWO) mode, the nexus-shared volume can be mounted by only one node or claimant at a time. ReadWriteOnce access mode still allows multiple pods to access the volume when the pods are running on the same node.
60+
```
61+
apiVersion: v1
62+
items:
63+
- apiVersion: v1
64+
kind: PersistentVolumeClaim
65+
metadata:
66+
name: test-pvc
67+
namespace: default
68+
spec:
69+
accessModes:
70+
- ReadWriteOnce
71+
resources:
72+
requests:
73+
storage: 5Gi
74+
storageClassName: nexus-shared
75+
volumeMode: Filesystem
76+
volumeName: TestVolume
77+
status:
78+
accessModes:
79+
- ReadWriteOnce
80+
capacity:
81+
storage: 5Gi
82+
phase: Bound
83+
```
84+
85+
#### Read Write Many (RWX)
86+
87+
In Read Write Many (RWX) mode, the nexus-shared volume can be mounted by multiple nodes or claimants at the same time.
88+
```
89+
apiVersion: v1
90+
items:
91+
- apiVersion: v1
92+
kind: PersistentVolumeClaim
93+
metadata:
94+
name: test-pvc
95+
namespace: default
96+
spec:
97+
accessModes:
98+
- ReadWriteMany
99+
resources:
100+
requests:
101+
storage: 5Gi
102+
storageClassName: nexus-shared
103+
volumeMode: Filesystem
104+
volumeName: TestVolume
105+
status:
106+
accessModes:
107+
- ReadWriteMany
108+
capacity:
109+
storage: 5Gi
110+
phase: Bound
111+
```
112+
34113
## Storage appliance status
35114

36115
The following properties reflect the operational state of a storage appliance:

0 commit comments

Comments
 (0)