Bug 1661938 - [RFE] Provide image with OpenJRE
Summary: [RFE] Provide image with OpenJRE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: ImageStreams
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Ben Parees
QA Contact: XiuJuan Wang
Depends On:
TreeView+ depends on / blocked
Reported: 2018-12-24 16:15 UTC by Stuart Auchterlonie
Modified: 2018-12-24 16:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-12-24 16:37:15 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Stuart Auchterlonie 2018-12-24 16:15:41 UTC
3. What is the nature and description of the request?

Customer would like an image to use for deploying
java based applications that does not contain the
java development tools (JDK), but only contains the
runtime (JRE)

4. Why does the customer need this? (List the business requirements here)

Customer needs to be able to deploy java applications without
deploying the JDK into production.

5. How would the customer like to achieve this? (List the functional requirements here)

Provide an image with the JRE

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

Create image, and test that a pre-built java application
can run, but that none of the JDK tools are available.

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

None found.

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?


9. Is the sales team involved in this request and do they have any additional input?


10. List any affected packages or components.

Openshift Images

11. Would the customer be able to assist in testing this functionality if implemented?


Comment 2 Stuart Auchterlonie 2018-12-24 16:17:31 UTC
To clarify, this request is for JRE 8 to match the developer focused JDK 8

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