Update KEP to reflect volume cloning beta in 1.16

keps/sig-storage/20181111-extend-datasource-field.md

@@ -114,6 +114,8 @@ Currently the CSI provisioner already accepts the DataSource field in new provis
 
 To emphasize above, this feature will ONLY be available for CSI.  This feature wil NOT be added to In-tree plugins or Flex drivers, this is strictly a CSI only feature.
 
+It's important to note that we intentionally require that a source PVC be in teh same StorageClass as the PVC being created.  This is currently required because the StorageClass determintes characteristics for a volume like `fsType`.  Performing a clone from an xfs volume to an ext4 volume for example would not be acceptable, given that a storageClass can have unique information, cloning across storage classes is not something we're able to try and determine safely at this time.
+
 ### Risks and Mitigations
 
 The primary risk of this feature is requesting a PVC DataSource when using a CSI Driver that doesn't handle Cloning in a safe way for running applications.  It's assumed that the responsibility for reporting Clone Capabilities in this case is up to the CSI Driver, and if a CSI Driver is reporting Clone support that implies that they can in fact Clone Volumes without disrupting or corrupting users that may be actively using the specified source volume.
@@ -130,6 +132,9 @@ Given that the only implementation changes in Kuberenetes is to enable the featu
 
 ## Implementation History
 
+Update to beta status for 1.16 release
+There were no issues or changes made during the 1.15 release, e2e tests have been added, updating to beta status for 1.16
+
 ## Drawbacks [optional]
 
 ## Alternatives [optional]