Storage Protection was renamed to Storage Object in Use Protection (#7576)
* Storage Protection was renamed to Storage Object in Use Protection The K8s PR: https://github.com/kubernetes/kubernetes/pull/59901 renamed Storage Protection to Storage Object in Use Protection. That's why the same is also renamed in the documentation. * Moved Storage Object in Use Protection admission plugin description down according to alphabetic order.
This commit is contained in:
committed by
zacharysarah
parent
614d47c560
commit
b4ccb71c3b
@@ -2,7 +2,7 @@
|
||||
reviewers:
|
||||
- msau42
|
||||
- jsafrane
|
||||
title: Storage Protection
|
||||
title: Storage Object in Use Protection
|
||||
---
|
||||
|
||||
{% capture overview %}
|
||||
@@ -14,13 +14,13 @@ Persistent volume claims (PVCs) that are in active use by a pod can be protected
|
||||
|
||||
{% capture prerequisites %}
|
||||
|
||||
- The Storage Protection feature is enabled in a version of Kubernetes in which it is supported.
|
||||
- The Storage Object in Use Protection feature is enabled in a version of Kubernetes in which it is supported.
|
||||
|
||||
{% endcapture %}
|
||||
|
||||
{% capture steps %}
|
||||
|
||||
## Storage Protection feature used for PVC Protection
|
||||
## Storage Object in Use Protection feature used for PVC Protection
|
||||
|
||||
The example below uses a GCE PD `StorageClass`, however, similar steps can be performed for any volume type.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user