Bug 1573228 - Need to EXPOSE port in golang s2i image so OpenShift properly reacts
Summary: Need to EXPOSE port in golang s2i image so OpenShift properly reacts
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: DevTools
Classification: Red Hat
Component: go-toolset-7-container
Version: go-toolset-7
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: 2018.2
Assignee: Derek Parker
QA Contact: Edjunior Barbosa Machado
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-30 14:27 UTC by Steve Speicher
Modified: 2018-06-04 17:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-04 17:45:55 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Steve Speicher 2018-04-30 14:27:34 UTC 
Description of problem:
OpenShift behaves differently when a port is exposed from a container via EXPOSE. For example, in the web console and oc new-app services and routes can be autocreated and provides a consistent and simple experience, like the other images.

See example from nodejs https://github.com/sclorg/s2i-nodejs-container/blob/master/8/Dockerfile#L6

Can we get EXPOSE 8080 added to the golang s2i image as well?
Note You need to log in before you can comment on or make changes to this bug.