You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: architecture/additional_concepts/storage.adoc
+18-19Lines changed: 18 additions & 19 deletions
Original file line number
Diff line number
Diff line change
@@ -107,22 +107,21 @@ PVs by including a `persistentVolumeClaim` in their pod's volumes block. See
107
107
xref:pvc-claims-as-volumes[below] for syntax details.
108
108
109
109
[[pvcprotection]]
110
-
111
110
=== Persistent Volume Claim Protection
112
111
113
112
[NOTE]
114
113
====
115
-
Persistent Volume Claim Protection is an alpha feature and may change in a future release of {product-title}.
114
+
PVC protection is an alpha feature and may change in a future release of {product-title}.
116
115
====
117
116
118
-
The purpose of the PVC protection is to ensure that PVCs in active use by a pod are not removed from the system as this may result in data loss.
117
+
The purpose of PVC protection is to ensure that PVCs in active use by a pod are not removed from the system, as this may result in data loss.
119
118
120
119
[NOTE]
121
120
====
122
-
PVC is in active use by a pod when the the pod status is `Pending` and the pod is assigned to a node or the pod status is `Running`.
121
+
A PVC is in active use by a pod when the the pod status is `Pending`, and the pod is assigned to a node or the pod status is `Running`.
123
122
====
124
123
125
-
When the PVC protection feature is enabled, if a user deletes a PVC in active use by a pod, the PVC is not removed immediately. PVC removal is postponed until the PVC is no longer actively used by any pods.
124
+
When the PVC protection feature is enabled, if a user deletes a PVC in active use by a pod, the PVC is not immediately removed. PVC removal is postponed until the PVC is no longer actively used by any pods.
126
125
127
126
You can see that a PVC is protected when the PVC's status is `Terminating` and the `Finalizers` list includes `kubernetes.io/pvc-protection`:
To enable PVC protection, see xref:../../install_config/configuring_pvc_protection.adoc#install-config-configuring-pvc-protection[Configuring Persistent Volume Claim Protection].
143
143
144
144
[[releasing]]
145
-
146
145
=== Releasing
147
146
148
147
When a user is done with a volume, they can delete the PVC object from the API
@@ -173,7 +172,7 @@ If supported by appropriate volume plug-in, recycling performs a basic scrub (`r
173
172
174
173
[WARNING]
175
174
====
176
-
The `recycle` reclaim policy is deprecated in favor of dynamic provisioning and it will be removed in future releases.
175
+
The `recycle` reclaim policy is deprecated in favor of dynamic provisioning and is removed starting in {product-title} 3.6.
177
176
====
178
177
179
178
ifdef::openshift-origin,openshift-enterprise[]
@@ -290,7 +289,7 @@ Future attributes may include IOPS, throughput, etc.
290
289
=== Access Modes
291
290
292
291
A `PersistentVolume` can be mounted on a host in any way supported by the
293
-
resource provider. Providers will have different capabilities and each PV's
292
+
resource provider. Providers have different capabilities and each PV's
294
293
access modes are set to the specific modes supported by that particular volume.
295
294
For example, NFS can support multiple read/write clients, but a specific NFS PV
296
295
might be exported on the server as read-only. Each PV gets its own set of access
@@ -352,7 +351,7 @@ Before draining the node, first ensure the pods that use these volumes are
352
351
deleted.
353
352
====
354
353
355
-
The table below lists the access modes supported by different persistent volumes:
354
+
The table below lists the access modes supported by different PVs:
volume claim (PVC) protection] feature enabled. This feature ensures that PVCs
16
+
in active use by a pod are not removed from the system, as this may result in
17
+
data loss.
15
18
16
19
[NOTE]
17
20
====
18
-
Persistent Volume Claim Protection is an alpha feature and may change in a future release of {product-title}.
21
+
PVC protection is an alpha feature and may change in a future release of {product-title}.
19
22
====
20
23
21
24
[[local-volume-enabling-local-volumes]]
22
-
=== Enable Persistent Volume Claim Protection
23
-
Enable the `PVCProtection` feature gate on all masters and nodes.
25
+
=== Enable PVC Protection
24
26
25
-
. Edit or create the master configuration file on all masters (*_/etc/origin/master/master-config.yaml_* by default) and add `PVCProtection=true` under the `apiServerArguments` and `controllerArguments` sections and add `PVCProtection` admission plugin configuration under the `admissionConfig` section:
27
+
To enable the `PVCProtection` feature gate on all masters and nodes:
28
+
29
+
. Edit or create the master configuration file on all masters (*_/etc/origin/master/master-config.yaml_* by default). Add `PVCProtection=true` under the `apiServerArguments` and `controllerArguments` sections, and add `PVCProtection` admission plugin configuration under the `admissionConfig` section:
26
30
+
27
31
[source, yaml]
28
32
----
@@ -46,13 +50,13 @@ kubernetesMasterConfig:
46
50
...
47
51
----
48
52
49
-
. On all nodes, edit or create the node configuration file (*_/etc/origin/node/node-config.yaml_* by default)and add `PVCProtection=true` fetaure gate under `kubeletArguments`.
53
+
. On all nodes, edit or create the node configuration file (*_/etc/origin/node/node-config.yaml_* by default), and add the `PVCProtection=true` feature gate under `kubeletArguments`:
50
54
+
51
55
[source, yaml]
52
56
----
53
57
kubeletArguments:
54
-
feature-gates:
55
-
- PVCProtection=true
58
+
feature-gates:
59
+
- PVCProtection=true
56
60
----
57
61
58
-
. On all masters and nodes, restart OpenShift for the changes to take effect.
62
+
. On all masters and nodes, restart {product-title} for the changes to take effect.
0 commit comments