1729330 – Carry VolumePVCDataSource feature in OCP 4.2

Bug 1729330 - Carry VolumePVCDataSource feature in OCP 4.2

Summary: Carry VolumePVCDataSource feature in OCP 4.2

Keywords:
Status:	CLOSED NOTABUG
Alias:	None
Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	openshift-apiserver
Sub Component:
Version:	4.2.0
Hardware:	All
OS:	All
Priority:	unspecified
Severity:	high
Target Milestone:	---
Target Release:	---
Assignee:	Stefan Schimanski
QA Contact:	Xingxing Xia
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2019-07-12 00:02 UTC by John Griffith
Modified:	2019-07-12 00:03 UTC (History)
CC List:	2 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2019-07-12 00:03:51 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

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

Note You need to log in before you can comment on or make changes to this bug.