From 18ba9a10f483a917254d48bb00068a2254cafdfa Mon Sep 17 00:00:00 2001 From: Karen Bradshaw Date: Sat, 18 Aug 2018 09:31:00 -0400 Subject: [PATCH] Clean up feature state includes (#9895) --- .../storage-object-in-use-protection.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/content/en/docs/tasks/administer-cluster/storage-object-in-use-protection.md b/content/en/docs/tasks/administer-cluster/storage-object-in-use-protection.md index d5e90dd349..3065c42cf6 100644 --- a/content/en/docs/tasks/administer-cluster/storage-object-in-use-protection.md +++ b/content/en/docs/tasks/administer-cluster/storage-object-in-use-protection.md @@ -15,8 +15,11 @@ Persistent volume claims (PVCs) that are in active use by a pod and persistent v {{% capture prerequisites %}} The Storage Object in Use Protection feature is enabled in one of the below Kubernetes versions: -- {% assign for_k8s_version = "1.10" %} {% include feature-state-beta.md %} -- {% assign for_k8s_version = "1.11" %} {% include feature-state-stable.md %} + +{{< feature-state for_k8s_version="v1.10" state="beta" >}} + + +{{< feature-state for_k8s_version="v1.11" state="stable" >}} {{% /capture %}} @@ -186,7 +189,7 @@ Events: - Create a second pod that uses the same PVC: -``` +```yaml kind: Pod apiVersion: v1 metadata: @@ -212,11 +215,11 @@ spec: - Verify that the scheduling of the second pod fails with the below warning: -``` +```shell Warning FailedScheduling 18s (x4 over 21s) default-scheduler persistentvolumeclaim "slzc" is being deleted ``` -- Wait until the pod status of both pods is `Terminated` or `Completed` (either delete the pods or wait until they finish). Afterwards, check that the PVC is removed. +- Wait until the pod status of both pods is `Terminated` or `Completed` (either delete the pods or wait until they finish). Afterwards, check that the PVC is removed. ## Storage Object in Use Protection feature used for PV Protection