Added tag at the top of each new area.

docs/admin/admission-controllers.md

@@ -330,7 +330,7 @@ of an object, so that only users with "update" permission to the `finalizers`
 subresource of the referenced *owner* can change it.
 
 ### Persistent Volume Claim Protection (alpha)
-
+{% assign for_k8s_version="v1.9" %}{% include feature-state-alpha.md %}
 The `PVCProtection` plugin protects Persistent Volume Claims (PVCs) that are being actively used by a pod from being deleted by adding `kubernetes.io/pvc-protection` finalizer to newly created PVCs.
 In case a user deletes a PVC that is not actively used by a pod the PVC's finalizer is removed by PVC Protection Controller.
 

docs/concepts/storage/persistent-volumes.md

@@ -54,7 +54,7 @@ dynamic provisioning for themselves.
 To enable dynamic storage provisioning based on storage class, the cluster administrator
 needs to enable the `DefaultStorageClass` [admission controller](/docs/admin/admission-controllers/#defaultstorageclass)
 on the API server. This can be done, for example, by ensuring that `DefaultStorageClass` is
-among the comma-delimited, ordered list of values for the `--admission-control` flag of 
+among the comma-delimited, ordered list of values for the `--admission-control` flag of
 the API server component. For more information on API server command line flags,
 please check [kube-apiserver](/docs/admin/kube-apiserver/) documentation.
 
@@ -71,6 +71,7 @@ Pods use claims as volumes. The cluster inspects the claim to find the bound vol
 Once a user has a claim and that claim is bound, the bound PV belongs to the user for as long as they need it. Users schedule Pods and access their claimed PVs by including a persistentVolumeClaim in their Pod's volumes block. [See below for syntax details](#claims-as-volumes).
 
 ### Persistent Volume Claim Protection
+{% assign for_k8s_version="v1.9" %}{% include feature-state-alpha.md %}
 In case the [PVC protection alpha feature](/docs/tasks/administer-cluster/pvc-protection/) is switched on, a PVC is being actively used by a pod and a user deletes the PVC the PVC is not deleted immediately, but the PVC deletion is postponed until it is not actively used by any pods.
 
 Such situation is indicated by the `Terminating` status of the PVC and the presence of the `kubernetes.io/pvc-protection` finalizer in the `Finalizers` list as shown below:
@@ -473,4 +474,3 @@ and need persistent storage, we recommend that you use the following pattern:
   default.
   At some point, the alpha annotation will cease to have meaning, but the unset
   `storageClass` field on the PVC will have the desired effect.
-

docs/tasks/administer-cluster/pvc-protection.md

@@ -6,7 +6,7 @@ title: Persistent Volume Claim Protection
 ---
 
 {% capture overview %}
-{% include feature-state-alpha.md %}
+{% assign for_k8s_version="v1.9" %}{% include feature-state-alpha.md %}
 
 As of Kubernetes 1.9, persistent volume claims (PVCs) that are actively used by a pod can be protected from pre-mature delettion.