Bug 1379327

Summary:	Support HTTP/2 protocol between client and Openshift
Product:	OpenShift Container Platform	Reporter:	Jaspreet Kaur <jkaur>
Component:	RFE	Assignee:	Derek Carr <decarr>
Status:	CLOSED WONTFIX	QA Contact:	Johnny Liu <jialiu>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.2.0	CC:	aos-bugs, byount, jkaur, jokerman, jupittma, mbarrett, mmariyan, mmccomas, mrobson, ofeodoro, rhowe, schoudha, simon.gunzenreiner, sreber, ykonotopov
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1480764 (view as bug list)		Environment:
Last Closed:	2019-06-12 11:55:14 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:
Bug Depends On:
Bug Blocks:	1480764

Description Jaspreet Kaur 2016-09-26 11:44:28 UTC

3. What is the nature and description of the request?
The customer would like for OpenShift to move away from using SPDY between client (e.g. UI or CLI) to a standard web protocol.

4. Why does the customer need this? (List the business requirements here)
The customer needs to run the OpenShift API behind a Web Application Firewall. For this, OpenShift may not use non-standard protocols such as SPDY.

We have a hard requirement to run the client facing part of OpenShift (everything accesses by either Console or CLI) behind a WAF. While HTTP/2 is already challenging, SPDY is not supported by the major WAF products.


5. How would you like to achieve this? (List the functional requirements here)
Potentially migrating away from SPDY to HTTP/2 could be an option.

https://docs.openshift.com/enterprise/latest/architecture/additional_concepts/port_forwarding.html

Comment 6 Eric Rich 2018-03-12 13:54:36 UTC

This bug has been identified as a dated (created more than 3 months ago) bug. 
This bug has been triaged (has a trello card linked to it), or reviewed by Engineering/PM and has been put into the product backlog, 
however this bug has not been slated for a currently planned release (3.9, 3.10 or 3.11), which cover our releases for the rest of the calendar year. 

As a result of this bugs age, state on the current roadmap and PM Score (being below 70), this bug is being Closed - Differed, 
as it is currently not part of the products immediate priorities.

Please see: https://docs.google.com/document/d/1zdqF4rB3ea8GmVIZ7qWCVYUaQ7-EexUrQEF0MTwdDkw/edit for more details.

Comment 12 Kirsten Newcomer 2019-06-12 11:55:14 UTC

With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers.  Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant.

This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. 

If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new 

Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new 

As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.