Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1729330

Summary:	Carry VolumePVCDataSource feature in OCP 4.2
Product:	OpenShift Container Platform	Reporter:	John Griffith <jgriffith>
Component:	openshift-apiserver	Assignee:	Stefan Schimanski <sttts>
Status:	CLOSED NOTABUG	QA Contact:	Xingxing Xia <xxia>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	aos-bugs, mfojtik
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-07-12 00:03:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description John Griffith 2019-07-12 00:02:19 UTC

Description of problem:

As a CNV on OCP user I would like to be able to take advantage of backend devices that provide smart-cloning.

Version-Release number of selected component (if applicable):

Propose carry of VolumePVCDataSource feature-gate in OCP 4.2, this feature is currently Alpha in Kubernetes 1.15.  This is however a low risk implementation and simply ignores or processes the DataSource field in a new PVC request.

This feature is marked fro beta in 1.16 with no API changes since its introduction in 1.15 and is very low risk.

PR proposing carry is here:  https://github.com/openshift/origin/pull/23241#issuecomment-504471766